Developers

Webhooks

Your systems hear what happens in your workspace: signed calls for the events you pick, retried and logged.

The events

  • Partners: created, updated, deleted, status changed, tier changed, manager changed.
  • Payout methods: created, updated.
  • Form requests: created, updated, deleted.
  • Conversions: created, updated, status changed.
  • Settlements and payments: settlement created, payment status changed.
  • Offers: created, updated, deleted; access granted, access revoked.
  • Postbacks: failed.
  • Whitelabels: created, updated, deleted.

Making one

  1. Settings › Developers › Webhooks › New webhook: your endpoint URL and the events.
  2. Only send when (optional): rules on the record's fields, all or any of them, comparing with a value, a list or another field.
  3. What to send: Compatible (short shapes an existing integration expects) or Full record (every field, with before and after values for changes). The example updates as you choose.
  4. Extra headers, if your endpoint needs them.

Checking the signature

Each call has a Signature header: the HMAC-SHA256 of the body with your webhook's signing secret. The secret is shown once when you make the webhook; New secret replaces it.

Deliveries

  • A call your server does not answer well is retried.
  • The delivery log shows every call, its attempts and what was sent; Send again repeats one.
  • Send test sends an event with your latest real record (or a sample).
  • After 20 failures in a row the webhook pauses itself and you get an alert. Fix the endpoint, then Resume.

Checked against the app on October 18, 2026