Webhooks

Listen for events so your integration can automatically trigger reactions.

All important activity on your ZWITCH account is recorded as an event. We use webhooks to notify you about important events on your account. These webhooks contain details about the event such as changes that occurred and the resources impacted by the change.

We send webhooks as HTTP POST call to a URL configured by you. Webhook payloads use the JSON format.

We recommend you treat webhooks as asynchronous events and do not depend on them for time-sensitive actions. While we try to deliver webhooks to you within a few seconds, there could be delays due to network and technical issues.

🚧

Webhooks are Asynchronous

Webhooks are asynchronous. We do not recommend waiting for a webhook to perform time-sensitive actions.

For time-sensitive actions, we recommend polling our APIs instead.

You can use webhooks to automatically trigger asynchronous events in your systems. For example, the beneficiary.created event is triggered when a beneficiary is successfully added to an account. You can use the webhook event to inform your customer that the beneficiary has been successfully added and that they can now transfer funds to their beneficiary.

πŸ“˜

IP Addresses for Webhook

To ensure your integration is secure, configure your servers to accept webhooks only from the below IP Addresses.

  • 34.93.71.125
  • 35.200.170.197
  • 34.131.212.152
  • 34.131.8.99
  • 13.232.28.107
  • 13.235.156.72
  • 18.60.100.10
  • 18.60.219.107
  • 65.1.255.46
  • 65.2.1.68
  • 18.60.193.125
  • 18.60.183.167


What’s Next

Learn how to setup webhook endpoint URL.