How to Brand System-Generated Links with an API Domain
An API domain (also called branded domain) replaces the default domain in system-generated links — forms, surveys, calendars, trigger links, payment links, and review links. Set one at the agency level for global default; override per sub-account when needed.
System-generated links — the URLs Sparkforge creates for forms, surveys, calendars, trigger links, payment links, and review links — use a default domain unless you brand them. A custom API domain replaces that with your own subdomain (e.g. links.yourbusiness.com), which improves email deliverability and reinforces brand recognition.
Where the branded domain shows up
- Forms
- Surveys
- Calendar links
- Trigger links
- Payment links
- Review links
- Short links
Two configuration levels
| Level | Behavior |
|---|---|
| Agency (API Domain) | Default branded domain across every sub-account. |
| Sub-account (Branded Domain) | Specific to one sub-account; overrides the agency-level domain. |
Configure at the agency level
Step 1: open the settings
Go to Agency View > Agency Settings > Company > Whitelabel > Domains.
Step 2: add the domain
Click Add Domain. The domain connect wizard launches and can create the CNAME automatically with most major registrars.
Step 3: configure DNS
If automatic setup isn't available for your registrar, create a CNAME manually in your DNS:
- Name: the chosen subdomain (e.g.
links). - Target:
brand.ludicrous.cloud
Scroll to the bottom of the Company page and click Update Company to save.
Configure at the sub-account level
Step 1: open Business Profile
In the sub-account, go to Settings > Business Profile.
Step 2: enter the branded domain
In the Branded Domain field, enter the subdomain (e.g. links.yourclient.com).
Step 3: add and verify
Click Add Domain to launch the wizard, or create the CNAME manually using the same target as above. Scroll down and click Update Information to save.
Troubleshooting
- Updating an existing domain? Clear the existing domain field, save, re-enter the new subdomain, then save again. The two-step save forces a clean rewrite.
- Don't use this for development. The API domain only brands system-generated links. It is not a development host or general-purpose CNAME.
- Use a subdomain, not the root. Pointing your root domain (e.g.
yourbusiness.com) at the API domain target will conflict with your website hosting.
Frequently Asked Questions
Can I use my root domain as the API domain?
What if a sub-account doesn't have a branded domain set?
How long does DNS propagation take?
What's the CNAME target?
Will branding the link improve email deliverability?
Was this article helpful?
Thanks for the feedback.