> For the complete documentation index, see [llms.txt](https://docs.hostedhooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hostedhooks.com/developer-resources/subscribers.md). # Subscribers ### What are Subscribers? Webhook subscribers are individuals or organizations that have opted to receive updates from a particular provider through webhooks. These subscribers, who are typically the provider's customers or users of their platform, establish a subscription with the provider's application in order to receive webhooks. Each subscription allows the subscriber to specify one or more endpoints, or URLs, where they wish to receive webhooks for specific events. These events can range from simple notifications, such as a new user signing up, to more complex updates, such as a change in a user's account status. The subscriber can also manage their subscriptions and endpoints, for example by adding or removing them as needed. Through webhook subscriptions, subscribers can stay informed about important updates and changes from the provider's application in real-time, without the need to repeatedly check for updates. ### What can Subscribers do? As a webhook subscriber, you have several controls at your disposal to help manage your webhooks. These controls allow you to customize your subscription to suit your specific needs and preferences. Some of the key controls include: 1. Endpoint management: You can specify one or more endpoints, or URLs, where you wish to receive webhooks. This allows you to route webhooks to different systems or applications depending on the event. 2. Event selection: Providers allow you to choose the events you want to receive by adding them to your endpoint. For example, you may only want to receive webhooks for updates related to a specific user or account. 3. Authentication: Some providers may require you to use a signing secret or SSL to receive your webhook. This would be in the form of a secret token. 4. Retries and Error handling: Some providers may allow you to set retry policies or error handling options to ensure that webhooks are delivered successfully. 5. Notifications: Some providers may allow you to set whether you receive notifications for webhook events (failure notifications for example). These controls give webhook subscribers the flexibility and granularity to manage their webhooks, and to configure them to suit their specific needs and preferences. Webhooks provide an efficient and real-time way for subscribers to receive updates from the providers' applications, and these controls make them even more powerful. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hostedhooks.com/developer-resources/subscribers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.