Discover our latest AI-powered innovations around faster payments, smarter workflows, and real-time visibility.Learn more →

Journal

Webhook Idempotency

We released an update to help our customers process their webhooks more safely.

Image of Matt Marcus
Matt MarcusCPO

We released an update to help our customers process their webhooks more safely. Webhooks may be sent more than once in some cases, like when the webhook is not successfully handled by the receiving party. When this happens, it can be difficult to know if the webhook has been sent already.

Each webhook request will now include a unique ID. This ID will remain the same for every delivery attempt. That way, you can record which webhooks have already been processed so that you don’t process them multiple times.

The ID is sent through the X-Webhook-ID header. For more details, refer to the overview section on webhooks.

For more, head over to our complete API documentation.

Try Modern Treasury

See how smooth payment operations can be.

Talk to sales
What's new

Our Latest Articles

View All