# Webhooks FAQ ## How do I register a Webhook with Mews? [Contact support](/connector-api/contact-support.md) with details of your Webhook endpoint URL. ## Are there special considerations for setting up a Webhook server? The server must expose an endpoint accessible from the Mews infrastructure and can receive incoming `POST` HTTP requests with JSON content type. No special `content-type` headers are used. The server must respond in a timely manner (within 5 seconds). ## How can I authenticate Mews? To confirm that a request to your Webhook endpoint originates from Mews, we can add a shared secret token to the URL, as follows: ![Webhook authentication](/files/BfZ0GJj2gaEjncuGLVS9) To use this authentication, send us the token you wish to use via [contact support](/connector-api/contact-support.md). The token should be kept secret and not shared with anyone except Mews. ## How should the server respond to a Webhook request? The server must respond with an HTTP status code indicating a success (e.g. `200 OK`, `202 Accepted`, or `204 No Content`). The server can respond with a redirection status code which doesn't change the request method (e.g. `307 Temporary Redirect` or `308 Permanent Redirect`) and the event message will be sent to the new location. If the server cannot process the request, it should respond with an appropriate error status code (i.e. `4xx` or `5xx` status codes). When the server responds with an error status code, the event message delivery will be retried, see [Do you attempt to resend failed Webhook messages?](#do-you-attempt-to-resend-failed-webhook-messages). ## Do you attempt to resend failed Webhook messages? If an event message fails to be delivered (either HTTP error code is received or the server doesn't respond within 5 seconds), the message will be re-sent after a few minutes. If the message isn't received after repeated attempts, it will be discarded. ## When should I use Webhooks? See [Ways to communicate](/connector-api/events/communicate.md). ## How are Webhooks different to WebSockets? See [Ways to communicate](/connector-api/events/communicate.md). ## What events can I create Webhooks for? See the Webhook reference pages for the list of currently supported events: * [General Webhooks](/connector-api/events/wh-general.md) * [Integration Webhooks](/connector-api/events/wh-integration.md) ## What does an event message look like? See the Webhook reference pages for details of the request body: * [General Webhooks](/connector-api/events/wh-general.md) * [Integration Webhooks](/connector-api/events/wh-integration.md) ## What is the frequency of event generation? The frequency at which events are created in the Mews system depends on the type of event and on the level of activity. Note however there may be a time lag of up to several minutes from when the event occurs to when the actual Webhook request is made. See [When are Webhooks generated?](/connector-api/events/communicate.md#when-are-webhooks-generated). ## Can I see what Webhooks are configured? Webhooks are set up in the system administration, please [contact support](/connector-api/contact-support.md) for information about what Webhooks are configured on the system for your application. ## Can I set up multiple Webhooks? Only one endpoint URL for [General Webhooks](/connector-api/events/wh-general.md) and one endpoint URL for [Integration Webhooks](/connector-api/events/wh-integration.md) can be set up per integration client, i.e. per partner application. If you wish, you can use the same endpoint URL for both types of Webhook. ## Can I use Webhooks in an on-premise application? Although possible, it is generally not recommended to use Webhooks for on-premise solutions. The webhooks endpoint must be accessible from Mews infrastructure and we may update the API multiple times a year, which may require updates to your application. If pushing the updates to the on-premise solution is difficult then the solution won't scale well. ## Is it possible to disable sending some messages to Webhooks? Yes. Event messages are configured for each integration, please [contact support](/connector-api/contact-support.md) with your requirements and they can configure only the messages you want to receive. ## Can you give me a specific use case for Webhooks? A specific use case for Webhooks is described in [Event management - Managing availability block inventory and pickup](/connector-api/use-cases/events.md#managing-availability-block-inventory-and-pickup), but Webhooks are relevant to many use cases and are discussed in the relevant section - see [Use cases](/connector-api/use-cases.md). ## Is there a limit on the number of events in one Webhook? [General Webhooks](/connector-api/events/wh-general.md) carry multiple events that have occurred at the same time. Yes, there is an upper limit on the number of messages carried, before rolling over to a new message. This number is a system parameter, currently in the order of hundreds, but Mews reserves the right to adjust this value for performance reasons. ## I want an event not currently supported The list of supported events is always under review and may be extended in future. If there is a system event that you are particularly interested in, please submit your request via the Mews [Product Ideas Forum](https://feedback.mews.com/). We can't provide any guarantees, but we are very interested to know what kind of features our customers and partners are requesting. --- # Agent Instructions: 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: ``` GET https://docs.mews.com/connector-api/events/wh-faq.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.