Custom Subdomains
How to use custom subdomains for your webhook endpoints
Registering your own subdomain (e.g., your-company.hooks.webhookrelay.com
) is highly recommended. It provides a stable, reusable public URL for your inputs, allowing easy integration with other tools and services. You can point this subdomain to different buckets as needed, offering flexibility and control over your webhook endpoints.
Why Use a Custom Subdomain?
When you create a bucket in Webhook Relay, it gets a unique, randomly generated public URL. While functional, these URLs can be long and difficult to remember. If you delete and recreate a bucket, the URL changes, requiring you to update it in all services sending webhooks to that endpoint.
Custom subdomains solve this by giving you a persistent, memorable address for your webhooks.
Key Benefits:
- Stable & Reusable URLs: Once you set up
your-company.hooks.webhookrelay.com
, this URL remains constant. Even if you change the underlying bucket it points to, your webhook providers won't need to update their configurations. - Easier to Remember: A custom subdomain is significantly easier to recall and share than a long, random string of characters. This simplifies debugging and communication with your team.
- Brand Consistency: Reinforce your brand by using a subdomain that reflects your company or project name.
- Seamless Bucket Switching: Need to redirect webhooks to a new bucket for testing, development, or a new version of your application? Simply update your custom subdomain's target destination in Webhook Relay. There's no need to change the webhook URL in the source applications.
- Simplified Configuration: Reduce the hassle of updating webhook URLs across multiple third-party services every time your input destination changes.
By using a custom subdomain, you create a more robust, manageable, and professional webhook infrastructure.