Setting up Webhooks

This page will help you set up and start using webhooks to receive real-time notifications from Bitpanda directly to your application. Follow these steps to configure your API URLs and begin leveraging the power of event-driven data delivery.

Step 1: Register your callback URL

  • Configure endpoint: Your application must have a publicly accessible endpoint to receive webhook notifications. This URL will be where we send JSON data when an event occurs.
  • Register URL & subscribe to events: Once available, pass this URL to our solution engineer together with the events that are relevant to your application.

There are two main options for differentiating between webhook calls:

  • URLs with different routes: You can set up a unique callback URL for each notification type, such as www.123.com/webhooks/webhook-1, webhook-2, etc. This approach allows you to process each event separately based on its endpoint, making it straightforward to distinguish between notification types.
  • Single URL with custom headers: Alternatively, if you prefer to use a single callback URL, we can configure custom headers for each notification type. This setup will enable you to identify the event type through the header, allowing flexible handling of different notifications within a single endpoint.

Each notification type also has a distinct payload structure, which aids in differentiation if using a single URL. Additionally, you have the option to activate notification types one at a time, providing control over your integration and easing testing.

Let us know which approach you would like to proceed with.

Step 2: Setup Security Configs

Configure the Bitpanda IPs to make sure the requests are correctly filtered.

Step 3: Handle Incoming Data

Code and test your endpoint to accept POST requests. Ensure it can parse the JSON payload and handle different types of events according to your business logic as detailed in the following subsections. Note that you should process the events in an idempotent way as the events might be sent one or multiple times.