Webhooks

Webhooks let you subscribe to events in Paddle. When a subscribed event occurs, Paddle sends a notification that includes a JSON payload with the updated entity.

They're great for things like:

• Managing access to features in your app depending on a customer's subscription or invoice status
• Syncing information with other systems that your business uses, like a CRM or ERP solution
• Setting up notifications or automations

You can set up URLs to receive webhooks and the types of events you'd like to get from your Paddle dashboard under Developer Tools > Notifications.

Respond to events

The server that you set to receive events from Paddle should respond with an HTTP 200 status code within 5 seconds. This lets Paddle know that you successfully received the message.

If your server sends another kind of status code or doesn't respond, Paddle automatically retries using an exponential backoff schedule. We retry 60 times for just under 3 days. The first 20 attempts happen in the first hour, with 47 in the first day and 60 overall.

Use an exponential backoff calculator to visualize retries from the date now. Use these values:

Allow Paddle IPs

To make sure you receive events from Paddle, we recommend that you add Paddle webhook IP addresses to your allowlist.

1
2
3
4
5
6
134.232.58.13
234.195.105.136
334.237.3.244
435.155.119.135
552.11.166.252
634.212.5.7

For security, only trust events that originate from Paddle webhook IP addresses.

Verify webhook signatures

Use the Paddle-Signature header included with each webhook to verify that received events are genuinely sent by Paddle.

See: Verify webhook signatures