Retry webhooks

Treezor provides a series of endpoints to resend webhooks.

Prerequisites – Service starting in October 2025

You can only retry webhooks emitted after October 1^st 2025. Please contact Treezor through the Support Center for requests anterior to that date.

Resending webhooks is a 3-step process:

1. Generate webhook history CSV file for a given time frame.
2. Request execution of the file to resend the events contained generated .CSV file (up to 20,000 events).
3. Retrieve the execution status of the resent events batch.

Information – The {webhooksBaseUrl} variable isn't your {baseUrl}

• https://webhook.sandbox.treezor.co in Sandbox
• https://webhook.api.treezor.co in Production

Generate webhook history CSV

You first need to generate the .CSV file containing the webhook events you wish to resend.

Parameters

Attribute	Type	Description
startAt	string	The date and time from which to retrieve the webhooks. Format: RFC3339.
endAt	string	The date and time up to which to retrieve the webhooks. Format: RFC3339.
webhook	string	Filter for a specific event, if need be. Example: wallet.create. See the Events description article for the list of events.

Request example

Endpoint: /retry/query

CURL

curl -X POST '{webhooksBaseUrl}/retry/query' \
	--header 'authorization: Bearer {accessToken}' \
	--header 'Content-Type: application/json' \
	-d '{payload}'

Here is an example of {payload}.

JSON

{
    "startAt": "2025-06-10T12:10:00+02:00",
    "endAt": "2025-07-08T00:00:00+02:00",
    "webhook": "merchantIdGroup.create"
}

Returns the following object:

JSON

{
    "queryId":"2bd5740a-528d-451d-a726-7f57c6d82008",
    "link": "https://your.csv.link",
    "expireIn": 300
}

If the .CSV file contains more than 20,000 events, you must adjust the time frame until you reach 20,000 or lower in order to move to step 2.

Resend events batch

Now that a .CSV file with a maximum number of 20,000 events has been generated, you can use the execution endpoint to resend all the events contained in the file.

Parameters

Attribute	Type	Description
queryId	string	The unique identifier of the query obtained in the first step.
delay	integer	The time between each webhook retry attempts in seconds, in order to not overload your servers. Can't exceed 1 hour (3600).

Request example

Endpoint: /retry/exec

CURL

curl -X POST '{webhooksBaseUrl}/retry/exec' \
	--header 'authorization: Bearer {accessToken}' \
	--header 'Content-Type: application/json' \
	-d '{payload}'

Here is an example of {payload}.

JSON

{
    "queryId":"2bd5740a-528d-451d-a726-7f57c6d82008",
    "delay": 10
}

Returns the following object:

JSON

{
    "executionId":"12345678-1234-1234-1234-123456789abc",
    "status": "IN_PROGRESS"
}

Retrieve the execution status

You can check whether the resend batch is completed using the dedicated request below with the executionId from the previous step.

Request example

Endpoint: /retry/exec/{executionId}

CURL

curl -X GET '{webhooksBaseUrl}/retry/exec/{executionId}' \
	--header 'authorization: Bearer {accessToken}'

Returns the following object, with the status valued to either IN_PROGRESS or DONE.

JSON

{
    "executionId":"12345678-1234-1234-1234-123456789abc",
    "status": "DONE",
    "lastEventAt": "2025-04-23T10:30:00Z"
}