Skip to main content
Neither platform lets an app claim a domain’s links on its own say-so. Both fetch a file from the domain and check the app is listed. Without it, your links open in a browser no matter how they are configured. 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

Expect the Dynamic Link host listed as verified.

iOS

Add applinks: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:
The Team ID is in your Apple Developer account under Membership.

Android (manual)

package_name is your application id, and sha256_fingerprints are the signing certificate fingerprints:
Include every certificate that signs a build you ship — debug, release, and Play App Signing. Google Play re-signs uploads with its own key, so the fingerprint from your local keystore alone is not enough and links will fail only in production.The Play Console shows the right one under Setup → App integrity. Auto mode already copies every fingerprint the destination site publishes.
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:
Use a Dynamic Link key (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

Both must be served over HTTPS with a valid certificate, with no redirect. The iOS file must be application/json and must not have a .json extension. Google’s own checker:
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 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.
App association requires a verified domain with a valid certificate. Check get_domain_verification_info and get_domain_ssl_status.
Neither platform follows redirects when fetching these files. http to https, or apex to www, is enough to break it.