This section is intended for consumers of the mluvii Public Api and is intended to provide detail on the use and handling of webhooks, thus contributing to the easier implementation of integrations with 3rd party systems.
After how long is the webhook deleted?
A non-functioning webhook is deleted after 3 days during which it fails to deliver a message to the defined URL.
What if the webhook fails to send to the URL?
In this case, a retry is triggered (up to 2 times). If even this is not enough, the message is discarded.
Does the "one event at a time" rule apply?
Yes, 1 webhook = 1 request
How do you know that the data is coming from mluvii?
You can add username: password to the URL [according to RFC-3986 (3.2.1. User Information)] , which you transform into the Authorize header, so you can do basic authentication.
Are duplicate events handled (e.g. 2x order cancellations)?
The TCP protocol acknowledges the delivery and the HTTP protocol defines the client server's acknowledgement response. In case of failure (client processes payload from mluvii before sending HTTP response to us), mluvii sends the same payload again. The processing of the payload by the client should be an idempotent operation.
Does the information about each event leave in the correct order?
Yes, events for a given entity type (session, email, user) leave in the order they occur.
Is the use of HTTPS required for webhook endpoints?
It is recommended, although we do not enforce it nowadays.
