We've updated our API endpoints to match what we use in our application. Some endpoints have been deprecated. See our Deprecated Endpoints page for migration details.
Set up and verify a custom domain for your QR codes.
Custom domains let your QR codes and short links resolve through your own sub-domain (for example offer.yourbrand.com) instead of the default scnv.io short URL.
Two routes exist in the app for this feature: /settings/domains and /account/domains. Live testing confirmed /account/domains is a redirect shim straight to /settings/domains (it renders nothing of its own), and the app’s own sidebar link — labeled Custom Domain under Settings — also points to /settings/domains. That’s the canonical, documented route below.
Open Settings > Custom Domain in the sidebar, or go directly to /settings/domains.
Custom Domains page with no domains added yet
Custom domains are a Pro-and-above feature. On a plan without domain access, this page shows an upgrade prompt instead of the setup flow below.
Click Add Domain. A drawer opens asking for the sub-domain name you want to use — the full name including the sub-domain, for example offer.myweb.com.
Step 1: entering the sub-domain name
An Advanced Settings section lets you disable case-sensitivity on this domain’s URL slugs before you continue — this can’t be changed later, so decide up front if you need it.
2
Add the DNS records
Once you continue, the domain is created and the drawer shows the exact DNS records to add at your registrar: a CNAME record pointing your sub-domain at Scanova’s target, and a TXT record (on @, the root) proving ownership.
The DNS records this domain needs, from the read-only details view
Click Verify. If both records resolve, the domain is marked verified immediately. If not — which is expected right after adding new DNS records — you’ll see a “could not verify yet” message:
Unable to verify your custom domain right now. Please note that sometimes it will take up to 24 hours before our system can recognise the changes on your subdomain. You can try and re-verify the domain after some time.
DNS propagation can take up to 48 hours in the worst case, even though the in-app copy says up to 24 hours for this specific message — both figures appear in the product depending on where you look, so treat “up to 48 hours” as the safe upper bound before assuming something is actually wrong.
Live-tested with a domain that has no real DNS records pointing at it: the domain was created successfully and immediately showed Unverified status, exactly as expected, since there was nothing for it to find.
Once a domain exists in your list, its row shows its verification status, whether it’s your Default domain, and a ··· menu:
A domain row with Unverified status, Reverify, Setup Again, and the row menu open
Reverify — re-checks DNS without restarting setup. Use this after you’ve actually added the records and given DNS time to propagate.
Setup Again — restarts the setup drawer at step 1 with the current host prefilled, in case you need to correct a typo. Since a domain name can’t be edited after creation, changing it here deletes the old entry and creates a new one — only after the replacement is confirmed and successfully created, so you’re never left with no domain at all.
Send setup instructions — emails the exact DNS records to whoever manages your DNS.
Root domain settings — choose what happens when someone visits the bare domain directly, without a QR code path: show a generic page, redirect to a URL, or show a custom landing page.
Delete — removes the domain; any QR codes using it fall back to the default Scanova short URL.
If you’d rather hand the DNS records to whoever manages your domain, use Send setup instructions from the row menu instead of copying each value yourself:
Emailing DNS setup instructions to another team
Enter a recipient email (for example, your IT team’s address) and an optional note, then send. The email includes the exact CNAME and TXT records for that domain — the same values shown in the DNS records step above.
A Custom SSL certificate option becomes available in the row’s ··· menu only after a domain is fully verified (both CNAME and TXT) — it wasn’t reachable during this testing pass since no verified domain was available in the test environment. From the source, the flow is: generate a CSR (certificate signing request) for the domain, submit it to your own certificate authority, then paste the signed certificate back in to activate it. On plans without this add-on, the dialog instead shows a “request access” form that reaches out to Scanova’s team directly, since Custom SSL has no self-serve upgrade path.
This is documented from source, not confirmed live — verify the exact CSR/upload flow against the running app before treating the details above as final.
