Skip to main content

Overview

Data events notify your application about the status of financial data fetch operations. These events fire after an FI Request is submitted and the Account Aggregator processes the data retrieval. Data events use eventType: "DATA" (or "DATA_EXT" for DATA_PUSH) and include linkRefNumbers arrays with per-account fetch status.

Data Fetch Flow

linkRefNumbers Structure

Data events include a linkRefNumbers array with per-account status details. In Type 1 (basic) payloads, only linkRefNumber and fiStatus are included. Type 2 (extended) payloads add FIP details.

Events

Sent when financial data has been successfully fetched and is ready for retrieval. Call the Get FI Data or Get All FI Data API to retrieve the data.

Basic Payload (Type 1)

Extended Payload (Type 2)

On receiving DATA_READY, call Get FI Data or Get All FI Data to retrieve the financial information. The linkRefNumbers array tells you which accounts have data available.
Sent when the FIP denies the data fetch request. This can happen when the FIP is unable or unwilling to share the requested data.

Basic Payload (Type 1)

Extended Payload (Type 2)

Sent when a data fetch session fails, typically due to a timeout at the FIP. The linkRefNumbers array shows TIMEOUT status for the affected accounts. Type 2 payloads include a sessionId for debugging.

Basic Payload (Type 1)

Extended Payload (Type 2)

Session failures are often transient. You can check the FI Request Status or submit a new FI Request to retry the data fetch.
Sent when a data fetch session expires before the FIP responds. Unlike SESSION_FAILED, this indicates the session’s time-to-live was exceeded rather than an explicit failure.

Basic Payload (Type 1)

SESSION_EXPIRED events may not include linkRefNumbers. Submit a new FI Request to retry the data fetch if the consent is still active.
Sent when FinPro pushes raw financial data directly in the webhook payload. This is an extended event (eventType: "DATA_EXT") that eliminates the need to call the Get FI Data API — the complete financial information is included inline in the data array.

Payload

data Array Structure

Each entry in the data array represents one financial account:
DATA_PUSH payloads can be large since they contain full financial data inline. Ensure your webhook endpoint can handle payloads up to several megabytes and process them asynchronously.
With DATA_PUSH, you do not need to call the Get FI Data or Get All FI Data APIs — the data is delivered directly in the webhook payload.

Integration Guidance