Skip to main content
Every time FirstPromoter attempts to send a webhook, a delivery record is created and tracked. You can inspect these records via the dashboard to debug failed deliveries.

Delivery statuses

Retry behaviour

When a delivery attempt fails (non-2xx response, timeout, or network error), FirstPromoter waits before retrying. The delay uses exponential backoff, roughly doubling with each attempt: Retries stop when the number of failed attempts reaches the max_retries value configured on the subscription (default: 10, configurable from 0–10). After that, the delivery is marked failed. At the default of 10, retries span roughly 17 hours from the first failure. Set max_retries to 0 on a subscription to disable retries entirely.

Delivery record fields

number
Internal ID of the delivery record.
string
The UUID of the event. Matches event_id in the payload.
string
The event type string, e.g. commission.updated.
string
created, updated, or deleted.
string
The type of the resource, e.g. referral.
number
The ID of the resource.
string
Current status: pending, delivered, retrying, or failed.
number
How many delivery attempts have been made so far.
number
The HTTP status code returned by your endpoint on the last attempt.
string
The first 1,000 characters of your endpoint’s response body.
string
A description of the last error (e.g., timeout message, HTTP error). Up to 1,000 characters.
object
For updated events, the fields that changed (same as changes in the payload).
object
The full JSON payload that was (or will be) sent to your endpoint.
string
ISO 8601 timestamp of the successful delivery. null until delivered.
string
When the delivery record was created.

Viewing deliveries

You can view delivery history for any subscription from the Settings → Integrations → Webhooks page in the dashboard. Click into a subscription to see all delivery attempts, their status, response codes, and error details.

Manually retrying a failed delivery

You can re-attempt a delivery directly from the dashboard without waiting for the automatic retry schedule, as long as it still has retry budget remaining (its attempts count is below the subscription’s max_retries). Navigate to the subscription’s delivery history and click Retry on the delivery.
A delivery only reaches failed status once it has exhausted the subscription’s max_retries, so a delivery that is already failed cannot be retried as-is — increase max_retries on the subscription first to free up retry budget, then retry the delivery.

Sending a test delivery

When setting up a new subscription you can send a test payload to your endpoint from the dashboard without needing to trigger a real event. Navigate to the subscription and click Send test. The test payload has "data": { "test": true } just like a real delivery.