Webhooks FAQ
Last updated
Was this helpful?
Last updated
Was this helpful?
There are no special considerations for setting up a Webhook server. It simply needs to be an endpoint that is accessible to the Mews system and can receive and process incoming HTTP requests with JSON content-type. No special content-type headers are used.
To confirm that a request to your Webhook endpoint originates from Mews, we can add a shared secret token to the URL, as follows:
HTTP status codes should be returned as normal, e.g. you can use HTTP status code 200 or 202 to indicate success. You should send 400 codes and 500 codes as normal for different failure conditions. Note that if an event message fails to be delivered (either a timeout occurs or an HTTP error code is received), then the message will be re-sent after an interval delay, but after three failed attempts it will be abandoned.
See the Webhook reference pages for the list of currently supported events:
See the Webhook reference pages for details of the request body:
Although possible, it is generally not recommended for on-premise solutions to use Webhooks, because we may update the API once or twice a year which may require updates to your application. In that case, if pushing the updates to the on-premise solution is difficult then the solution won't scale well.
Email with details of your Webhook endpoint URL.
To use this authentication, send us the token you wish to use via . The token should be kept secret and not shared with anyone except Mews.
See .
See .
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 .
Webhooks are set up in the system administration, please contact for information about what Webhooks are configured on the system for your application.
Only one endpoint URL for and one endpoint URL for 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.
Yes. Event messages are configured for each integration, please contact with your requirements and they can configure only the messages you want to receive.
A specific use case for Webhooks is described in , but Webhooks are relevant to many use cases and are discussed in the relevant section - see .
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.
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 . We can't provide any guarantees, but we are very interested to know what kind of features our customers and partners are requesting.
