Webhooks

Webhooks are used as a messaging channel, to keep line of business systems synchronized with events inside Upodi. A webhook cannot be used as a reliable state of an object or action. The webhook should be used for event notification in conjunction with the API.

Upodi sends webhooks to any public available webserver as HTTP POST. You can specify multiple endpoints in the Upodi application.

Upon an event, Upodi will trigger a webhook and try to send this notification to the endpoint(s). Timeout is set to 5 seconds. The webhook response is not captured by Upodi. It is a simple fire and forget event.

Summarized:

• Enable a public available web endpoint using HTTP (port 80) or HTTPS (port 443).
• Your endpoint must be live and capture the event within 5 seconds.
• Upodi do not catch any response code.
• Method is POST.
• "Signature" will correspond to the authenticity token, and can be used to verify the source.

Webhook body
A webhook holds various information and details. Please make a sample to monitor the response formats.

This is an example of a webhook body (customer, create event):

{
  "ID" : "f07b8521-4421-4de6-96a5-178cf498cfef",
  "Time" : 131516890300860922,
  "Signature" : YTYxNWEzMdItZTBgg5i00YWE4LTk5tu6rh2JiZmEyODk5OGMz,
  "Action" :"create",
  "Issuer" : {
    "Url" : "/Customer/create/0ea627de-158e-48b1-bcbb-7fe6058d191c",
    "Identifier":"0ea627de-158e-48b1-bcbb-7fe6058d191c"
  },
  "Data" : null,
  "Type" : 
  "Customer"
}

📘

Need to test a webhook?

Services like Webhook Site enable quick test of the webhook calls from Upodi. Setup a Webhook.site endpoint and add the URL to the Upodi webhook.

Events
The followings events are sent from Upodi, to endpoint configured under webhooks.