Dashlink serves both on your Dynamic Link domain. Association is host-wide, so a shared shortlink domain such as
dshl.in cannot carry it. Create a dedicated Dynamic Link domain (for example go.example.com or news.dshl.in) first.
You do not paste fingerprints or App IDs by default. Dashlink copies the files from the destination website of the dynamic links on that domain. If a link points at https://stagingapp.dashlink.ai/demo, Dashlink fetches stagingapp.dashlink.ai/.well-known/… and republishes it on the Dynamic Link host. AASA paths are rewritten to * so a back-half such as /Z39pGI matches.
What the app must declare
The OS will not intercept the tap unless the app lists the Dynamic Link host.Android
iOS
Addapplinks:news.dshl.in to the app’s Associated Domains entitlement.
Reading the current configuration
id is the domain id from get_user_domains. The response includes mirrored Android packages and iOS App IDs, association_mode, source hosts, last sync time, and the live assetlinks_url / aasa_url.
Auto vs manual
association_mode defaults to Auto. Saving a dynamic link enqueues a refresh; a daily job re-fetches so rotated signing certificates stay current. Use the dashboard Re-sync action, or set association_mode to Manual and write the child tables yourself when the destination site does not publish well-known files.
iOS (manual)
app_id is your Team ID and bundle identifier joined by a dot:
Android (manual)
package_name is your application id, and sha256_fingerprints are the signing certificate fingerprints:
Resolve the deep link from the app
When the OS intercepts the tap, the app receives the short URL and the edge never sees a browser click. Call the same URL as JSON so the app can route to content and the click is counted as an app open:dlk_sdk_…), not a REST key (dlk_live_). Browser 302s need no key.
Or send Accept: application/json. The body includes app_url, destination_url, fallback_url, platform, outcome (app_open, deferred_open, or deferred_miss), click_id, is_deferred, match_type, and UTM fields. platform=android or platform=ios overrides User-Agent detection when the app’s HTTP client would otherwise look like desktop.
The Android and iOS SDKs call this for you on live taps and on first open after a store install. See Receive for the JSON contract.
Verifying
application/json and must not have a .json extension.
Google’s own checker:
When links still open in a browser
The app does not declare the Dynamic Link host
The app does not declare the Dynamic Link host
Auto-mirrored files are not enough. Android needs an
autoVerify intent-filter for that host; iOS needs applinks: on Associated Domains.iOS caches the file
iOS caches the file
iOS fetches the association file at install time and caches it. After changing it, delete and reinstall the app — an update is not always enough.
The fingerprint does not match
The fingerprint does not match
The most common Android failure, and it only shows up in production builds. Check the Play Console fingerprint, not your local keystore. If Auto mode is on, confirm the destination site publishes the Play App Signing fingerprint.
The domain is a shortlink domain
The domain is a shortlink domain
Association is rejected on Shortlinks usage. Create a Dynamic Link domain and put the link there.
The domain is not verified
The domain is not verified
App association requires a verified domain with a valid certificate. Check
get_domain_verification_info and get_domain_ssl_status.There is a redirect in the way
There is a redirect in the way
Neither platform follows redirects when fetching these files.
http to https, or apex to www, is enough to break it.