Return the current DeepTap account, plan, and limits. Call this first to check the plan and how many domains/links are available before creating resources. Read the meta block for live usage and rate limits.

List all DeepTap domains for the account, with their iOS/Android config and AASA/assetlinks URLs.

Fetch one domain by id (e.g. 'dom_42'), including its iOS/Android settings and generated file URLs.

Create a DeepTap subdomain and configure iOS Universal Links and/or Android App Links. Pass name (the subdomain label, e.g. 'myapp' → myapp.deeptap.io). For working routing also set fallback_url and app_store_url / play_store_url. After creating, call verify_domain.

Update a domain's iOS/Android configuration (partial — only the fields you pass change). iOS caches AASA aggressively; existing installs may take up to 24h to pick up changes.

Fetch the domain's generated apple-app-site-association and assetlinks.json and check them against the configured app identifiers (reachable, valid JSON, appID/package match, fingerprints, paths). Run after create_domain/update_domain. Note: this checks what is verifiable server-side; rebuilding the app and on-device checks are still required.