Custom Domains
Serve connector URLs from a hostname you own, with TLS handled for you.
Hand partners and customers connector URLs on a hostname you own instead of connect.connic.co. The URL looks like part of your product, the TLS certificate is on your domain, and you can swap out the underlying connector without ever rotating the URL your partners hold.
Default
https://connect.connic.co/webhook/3b0a9d…Every project shares the same host.
Custom
https://hooks.acme.com/webhook/3b0a9d…Your hostname, same connector underneath.
The connector doesn't change — same ID, same signing secret, same configuration. Only the host in front of it.
Adding a domain
Add domains in Project Settings → Domains. You'll need:
- A subdomain you own — apex domains and wildcards aren't supported. ASCII only; use punycode for IDNs.
- DNS access to that subdomain. You'll add two records: a CNAME that routes traffic to Connic, and a TXT that proves ownership so a TLS certificate can be issued.
DNS propagation can take up to an hour. Once both records resolve, the domain becomes selectable on connectors.
Using a domain on a connector
Each connector has a Domain field in its create and edit dialog — pick a domain there and the connector's URL switches to the new host. There's no redeploy and no URL rotation: the connector ID, signing secret, and config are unchanged.
- The default URL stays live. Assigning a domain doesn't retire
connect.connic.co— both serve the same connector, so you can roll partners over one at a time. - Domains are project-scoped. One domain can serve connectors in any of the project's environments.
Removing a domain
Deleting a domain frees the hostname and automatically points any connectors that were using it back to the default host. Update third parties calling the old hostname first — they'll start getting 404s once the domain is gone.
Access control
Only Owners and Admins can add, remove, or reassign domains. Members can see which domain a connector is using. Every change is recorded in the audit log.
Troubleshooting
| Symptom | What to check |
|---|---|
| TXT stays Pending | Confirm the record exists at the exact name from the dashboard. dig TXT _acme-challenge.your.host should return the value Connic gave you. Some DNS providers strip the trailing label — paste the name as shown. |
| CNAME stays Pending | The CNAME must point to connect.connic.co. A flattened ALIAS or ANAME can work; an A record to an IP will not. |
| Domain goes to Error | Usually the records appeared briefly and were then changed or removed. The row shows the underlying reason. Delete the domain and re-add the hostname to restart the flow. |
| Active but partner gets 404 | The hostname routes correctly, but the path needs the connector's ID. Copy the full URL from the connector's detail drawer rather than constructing it by hand. |