Re-issue Callbacks & Exports

In cases where asset callback were not received, there are two ways to re-issue Web callbacks and Database exports.

Use the Dashboard -> Tools menu option
Use the /reissue API

The following sections details the API option.

Reissue Callbacks & Exports API

Send a HTTP POST request to re-issue web callbacks and database exports for assets uploaded within a specified time range. This API is asynchronous.

Authentication

Requires ASSET_ADMIN role API Key.
Requires X-Filespin-Api-Key: <API_KEY> header.

POST Request JSON

The request requires a time range. A complete JSON payload for the reissue request below:

{
  "start_date": "2017-06-01T00:00:00Z",
  "end_date": "2017-06-07T23:59:59Z"
}

Key	Type	Description
`start_date`	string	(Required) Start date of the time range in ISO 8601 format (`YYYY-MM-DDTHH:MM:SSZ`).
`end_date`	string	(Required) End date of the time range in ISO 8601 format (`YYYY-MM-DDTHH:MM:SSZ`). Must be after `start_date`. Must not exceed 7 days from `start_date`.

HTTP Response

HTTP Status code 202 Accepted implies the task has been queued successfully.

"Re-issue callbacks started for assets uploaded from 2017-06-01T00:00:00Z to 2017-06-07T23:59:59Z"

Status Code	Description
`202 Accepted`	The request has been accepted for processing. The operation is asynchronous; the API returns immediately after queuing the task.
`400 Bad Request`	Invalid date format or logic (e.g., `end_date` is before `start_date`, or range exceeds 7 days).
`403 Forbidden`	User does not have `ASSET_ADMIN` permission.

🚧
Constraints & Warnings

Time Limit: The time range (end_date - start_date) is limited to a maximum of 7 days.

Scope: Only assets belonging to the authenticated user are processed.

Resource Usage: Ensure receiving webhook and target database are setup for callbacks. Use caution when reissuing callbacks for large numbers of assets.