Custom URLs

By default, HookSense endpoints get a random slug like hooksense.com/w/k7t9p2x4. Custom URLs let you pick the slug — readable, branded, and stable across redeploys. Useful for shipping webhook setup instructions to customers, internal documentation, and any URL that ends up in someone else's config.

Setup

1. Open your endpoint and click Settings (gear icon)
2. Find the Endpoint slug field
3. Type your desired slug (e.g., acme-stripe-prod) and save
4. Your URL becomes https://hooksense.com/w/acme-stripe-prod

Old random slug stops resolving the moment the new one saves — make sure you've updated the URL in your provider's webhook settings before changing it.

Slug Rules

• 3–48 characters
• Lowercase letters, digits, and hyphens only — a-z, 0-9, -
• Must start with a letter or digit (no leading hyphen)
• Globally unique across HookSense — taken slugs surface a "not available" hint immediately
• Reserved words rejected: api, www, admin, app, docs, blog, pricing, login, signup, etc.

Naming Conventions

Slugs that age well:

• {tenant}-{provider}-{env} → acme-stripe-prod, acme-stripe-staging
• {provider}-{event-type} → stripe-checkout, github-pushes
• {team}-{integration} → billing-stripe, support-zendesk

Avoid: dates, version numbers, throwaway names — slugs that change force you to re-register webhooks with every provider.

Programmatic Updates

curl -X PATCH https://hooksense.com/api/endpoints/CURRENT_SLUG \
  -H "Content-Type: application/json" \
  --cookie "hs_session=..." \
  -d '{"slug":"new-desired-slug"}'

Returns 409 if the new slug is taken or 422 if it violates the rules. See API reference.

Custom URLs require Hook plan or above. For domain-level branding, see Custom Domains.