Export Ready Webhook


Overview

The ExportReady event fires when an export has finished generating and is available for download. Use this event to retrieve the report file automatically, without polling the API or waiting for an emailed link.

Trigger Conditions

This event is triggered when a transaction export completes, from one of two sources: an event-driven export subscription, which generates an export when Infinicept receives new transaction data from the processor; or a scheduled export, which runs on its configured daily schedule when set to deliver via webhook.

Payload Schema

The webhook body is the event data object serialized directly (no outer envelope).

Top-Level Fields

FieldTypeDescription
tenantSlugStringThe slug identifying the tenant the export belongs to.
exportIdStringUnique identifier (UUID) for the generated export.
perspectiveStringExpected value: Payfac
downloadUrlStringSecure, time-limited URL the report is downloaded from. The link is valid for seven days. After this time, the download link expires and the file is no longer accessible via download link or webhook replay. Re-run the export to generate a fresh file.
completedAtStringTimestamp indicating when the export finished generating. Example value: 2026-05-12 17:53:12.

Example Payload

{
  "tenantSlug": "onepayments",
  "exportId": "6664f794-23f7-46be-ad56-4559894d4c7f",
  "perspective": "Payfac",
  "downloadUrl": "https://infiniceptfundingapp.example.com/exports/6664f794-23f7-46be-ad56-4559894d4c7f",
  "completedAt": "2026-05-12 17:53:12"
}

The downloadUrl value above is illustrative. The real URL is a secure, expiring link generated per export.

Handling This Event

  1. Follow downloadUrl to retrieve the report file as soon as the event is received. The link expires after seven days, so download promptly rather than storing the URL for later use. After this time, the file is no longer accessible via download link or webhook replay. Re-run the export to generate a fresh file.
  2. Store exportId and tenantSlug to correlate the export with records in your own system and to deduplicate against repeat or replayed deliveries.
  3. Use perspective to route or label the report if you consume exports across more than one reporting perspective.


Did this page help you?