Guides
Custom domains
Serve your source URLs from your own hostname, such as hooks.acme.com, instead of hooks.getensue.com.
By default a source URL looks like https://hooks.getensue.com/in/<token>. With a custom domain, the same source is reachable at https://hooks.acme.com/in/<token>. Senders then never see Ensue’s hostname, and you can move providers without changing every sender’s webhook settings.
Add a domain
-
Open Settings → Domains, or
POST /v1/domainswith the hostname.curl -X POST https://api.getensue.com/v1/domains \ -H "authorization: Bearer ens_<key>" -H "content-type: application/json" \ -d '{ "hostname": "hooks.acme.com" }' -
The response lists the DNS records to create at your DNS provider:
Type Name Value CNAMEhooks.acme.comThe target Ensue gives you. TXT_acme-challenge.hooks.acme.comThe validation value Ensue gives you, so the certificate can be issued. -
Wait for the status to become active. Ensue checks pending domains every five minutes; Check now (
POST /v1/domains/:id/check) checks immediately.
When both the hostname and its TLS certificate are active, the same source tokens work on your hostname. The original hooks.getensue.com URL keeps working.
Good to know
- Add the
TXTrecord before you move theCNAME, so the certificate is issued without downtime. - If validation fails permanently, remove the domain and add it again.
- Over-quota traffic is blocked at the edge on custom domains too. See Usage and retention.
- Deleting a domain stops serving it straight away; senders still pointing at it will get connection errors.