Launch special — let's split the check with SPLITCHECK for 50% off
Share feedback →

features

Custom Domains

Use your own domain for webhook endpoints instead of the default hooksense.com URL.

Custom domains let webhook URLs live on your own brand — webhooks.yourapp.com instead of hooksense.com/w/abc123. Useful for white-label B2B integrations, customer-facing setup pages, and stable URLs that survive even if you migrate off HookSense later.

Setup

  1. Pick a subdomain on a domain you control (recommended: webhooks.yourapp.com or hooks.yourapp.com — apex domains aren't supported because of CNAME limitations).
  2. Add a CNAME record in your DNS provider: 
    webhooks.yourapp.com.  CNAME  cname.hooksense.com.
  3. In HookSense, open your endpoint and click Custom Domain in the toolbar.
  4. Enter the full domain (webhooks.yourapp.com) and click Verify.
  5. HookSense checks the CNAME and provisions a TLS certificate via Let's Encrypt. The domain becomes active when both succeed (usually 30–120 seconds).

How It Works

Once verified, any HTTPS request to webhooks.yourapp.com is routed to the bound endpoint. Headers and body are preserved exactly. Each domain is bound 1:1 to an endpoint — to point a domain at a different endpoint, unbind first.

TLS certificates auto-renew 30 days before expiration. No action required from you.

Multi-Path Routing

Want webhooks.yourapp.com/stripe and webhooks.yourapp.com/github to land on different endpoints? Bind the same custom domain to multiple endpoints; HookSense routes by the path segment after the host:

webhooks.yourapp.com/stripe  →  endpoint slug: stripe-prod
webhooks.yourapp.com/github  →  endpoint slug: github-prod

The path must match the endpoint slug exactly. Requests to unmatched paths return 404.

Troubleshooting

  • "CNAME not found" — DNS hasn't propagated. Check with dig CNAME webhooks.yourapp.com from a different network. Cloudflare proxied (orange cloud) records won't verify; set DNS-only (gray cloud) until verification, then re-enable proxy if desired.
  • "TLS provisioning failed" — your DNS provider blocks Let's Encrypt CAA records. Add letsencrypt.org to your CAA policy or remove CAA records.
  • "Certificate expired" — extremely rare; auto-renewal handles this. If it happens, click Re-verify.
  • SNI failures from older clients — HookSense requires SNI (TLS 1.2+). Java 7 and pre-2018 IoT clients may fail.

Custom domains require the Sense plan.

PreviousCustom ResponsesNext Endpoint Sharing