FlowMock

Domain verification

Point a custom subdomain at FlowMock so cookies and HTTPS behave.

On this page

The default FlowMock proxy URL works out of the box. But if your app uses cookie-based auth, you'll want a custom domain — a subdomain of your own that points at FlowMock via CNAME.

This guide covers verification. For the cookie implications, see Cookie auth.

Why verify a domain

  • Cookies work reliably on your own subdomain
  • Your QA URL looks like api-qa.yourcompany.com instead of p.flowmock.dev/…
  • HTTPS is handled by FlowMock once verification completes

Step 1: Add the domain

In your team settings → Domains, add the subdomain you want:

text
api-qa.yourcompany.com

FlowMock shows you a CNAME target — something like custom.flowmock.dev.

Step 2: Create the CNAME record

In your DNS provider (Cloudflare, Route 53, etc.), add:

TypeNameTarget
CNAMEapi-qa (or your subdomain)The target FlowMock provided

DNS propagation can take a few minutes to a few hours. Patience, or grab a coffee.

Step 3: Verify

Back in FlowMock, click Verify. FlowMock checks the CNAME record. Once it passes, the domain is active and linked to your proxy environment.

Step 4: Update your app

Point your app's API base URL to the new custom domain:

text
https://api-qa.yourcompany.com

Same paths, same everything — just a different host.

Re-verification

FlowMock periodically re-checks domain records. If you remove or change the CNAME, the domain may be marked unverified until you fix DNS.

Sandbox domains

FlowMock demo sandboxes use a separate verification flow with stricter rules. If you're setting up a sandbox environment, follow the in-dashboard prompts — they differ slightly from production custom domains.

Troubleshooting

Domain not verifying?

  • Confirm the CNAME points to the exact target FlowMock shows (no typos)
  • Check you're not mixing A and CNAME records on the same name
  • Wait for DNS propagation — dig api-qa.yourcompany.com CNAME is your friend
  • See Connect troubleshooting for more