Automatic retries cover transient failures while Bitso is delivering an event. After those attempts are exhausted, or if you need to replay events that already succeeded, use the retry endpoints.

Bitso stores webhook events for 60 days after they are created. After that they are deleted and can no longer be previewed or retried. When you copy request examples from the API Reference, replace from_date and to_date with a window that is at most 3 days long, not in the future, and not more than 60 days in the past.

Rules

• from_date and to_date are required. The interval must not exceed 3 days.
• from_date must be before to_date, no more than 60 days in the past.
• to_date must not be in the future.
• event must be one of the documented event types.
• delivered selects previously successful deliveries (true) or failed ones (false, the default).
• Events scheduled through this API receive one additional delivery attempt. Delivery is not immediate.
• Retrying events that were already delivered is allowed. Your endpoint must handle duplicates; see Best Practices.

Preview

Call Preview a webhook retry to count matching events without sending them. Use this to confirm the window and filters before you execute.

Execute

Call Execute a webhook retry to schedule matching events. A successful call returns 202 Accepted with the number of events queued.

Optionally set limit (minimum 1) to cap how many events are scheduled. The service caps a single execute call at 5,000 events.

Typical errors

The retry endpoints return 400 when the criteria are invalid. Common messages:

Request and response bodies are in the API Reference.