Webhooks FAQ
Last updated
Was this helpful?
Last updated
Was this helpful?
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.
A non-functioning webhook is deleted after 3 days during which it fails to deliver a message to the defined URL.
In this case, a retry is triggered (up to 2 times). If even this is not enough, the message is discarded.
Yes, 1 webhook = 1 request
You can add username: password to the URL [according to RFC-3986] , which you transform into the Authorize header, so you can do basic authentication.
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.
Yes, events for a given entity type (session, email, user) leave in the order they occur.
It is recommended, although we do not enforce it nowadays.