You can view event history and retry events directly in the Wise Developer Hub.
Webhook features in the developer hub are only available with the correct permission. Speak with your implementation team if you don’t have your access details.
Go to the Webhook > Events section in the developer hub.
The page displays a unified view of all webhook delivery events across all subscriptions for the current application.
The same events panel also appears embedded within the Subscription Detail page, pre-filtered to show only events for that subscription.
Each delivery displays:
- Status icons: Colour-coded circle indicating the delivery outcome:
- Green check = Delivered
- Red cross = Failed
- Orange alert = Abandoned
- Grey pending = Pending / Queued / Sending
- Event type: The event identifier (for example,
transfers#state-change) - Relative timestamp: When the last attempt was made (for example, "3 minutes ago"). Wider screens also include the absolute UTC timestamp.
Depending on how frequently your events are sent out, the list of events you are viewing can quickly become stale.
Click the Refresh button to reload the events list with the most up-to-date data.
Click the Filters button to filter the list by any of the following three filter types:
- Status
- Event type
- Date range
To see more details about an event, click any event in the list to open a detail panel. Click the same event again to close the panel.
The detail panel is divided into three sections: Subscription details, Delivery details, and Delivery attempts.
| Field | Description |
|---|---|
| Subscription ID | The subscription that triggered this delivery (click to copy). |
| Callback URL | The endpoint the payload was sent to. |
| Event type | The event type that was triggered. |
| Schema version | The payload schema version used. |
| Field | Description |
|---|---|
| Status | Current delivery status (colour-coded badge). |
| Delivery ID | Unique identifier for this delivery (click to copy). |
| Replayed from | If this is a retry, the original delivery ID it was replayed from (click to copy). |
| Error code | Machine-readable error code, if applicable. |
| Error message | Human-readable error description, if applicable. |
| Last HTTP status | The HTTP response code returned by your endpoint on the last attempt. |
| Created at | When the delivery was first created (UTC). |
| Last attempt | When the most recent delivery attempt was made (UTC). |
| Total attempts | Number of delivery attempts made so far. |
This is shown for any event for which delivery has been attempted more than once. Each row represents one attempt and shows:
- Timestamp: When the attempt was made (UTC).
- Result: The HTTP status code, or an error code if no HTTP response was received. Attempts are listed in reverse chronological order (most recent first).
While Wise does automatically retry webhook event delivery according to our retry policy, these retries can also sometimes fail or end up in an abandoned state. For deliveries with a Failed or Abandoned status, we provide a Retry delivery action next to the Delivery Details section header (see Event Delivery Details for what it looks like).
A few things to note about retries:
- Automatic retries of the same event share the same
X-Delivery-Id, which you should use as your idempotency key. - Each manual retry creates a new delivery record with a new delivery ID. You should check the original event wasn't already received before manually retrying.
- Manual retries can only be done in the Developer Hub portal at this time. You don't need to build anything into your integration to accommodate manual retries or map the new ID to the original.