The format of Fivaldi Event Notifications will include the following headers:
- `X-Fivaldi-Webhook-Id: <webhookId>`
- `X-Fivaldi-Signature: <HMAC SHA256 signature>`, a hash of the request body created using the secret key assigned to the webhook.
Partners are advised to confirm the integrity of the request. This can be done by hashing the request body with the secret key provided at the time of webhook creation, using the HMAC SHA256 algorithm. The resulting hash should then be compared to the value in the `X-Fivaldi-Signature` header to ensure it matches.
Body:
{
eventId: String - unique id for the event,
eventType: String - type of event,
customerId: String - customer id,
cuid: String - company unique id, if present for the event,
timestamp: String - UNIX format: "1725146096",
payload: String - event contents
}
Response:
Fivaldi expects a response with an HTTP 202 status from a partner within 5 seconds following an event notification request. If Fivaldi receives a different response or no response at all, it will attempt to resend the notification. This retry process will continue up to five times. If, after the fifth attempt, the response criteria are not met, Fivaldi will reject the event and disable the partner’s webhook. To reactivate their webhook, partners must submit a PATCH webhook request with the parameter `active=True`. It is important to note that any events occurring while the webhook is disabled will not be retrievable.
Oliko tästä vastauksesta apua? Kyllä Ei
Send feedback