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 useeventType: "DATA" (or "DATA_EXT" for DATA_PUSH) and include linkRefNumbers arrays with per-account fetch status.
Data Fetch Flow
linkRefNumbers Structure
Data events include alinkRefNumbers array with per-account status details. In Type 1 (basic) payloads, only linkRefNumber and fiStatus are included. Type 2 (extended) payloads add FIP details.
| Field | Type | Present In | Description |
|---|---|---|---|
linkRefNumber | string | Type 1 & 2 | Unique reference for the linked account |
fiStatus | string | Type 1 & 2 | Account-level status: READY, DENIED, or TIMEOUT |
fipName | string | Type 2 only | Display name of the Financial Information Provider |
fipId | string | Type 2 only | Identifier of the FIP |
maskedAccountNumber | string | Type 2 only | Masked account number (e.g., XXXXXXXX7300) |
Events
DATA_READY
DATA_READY
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)
DATA_DENIED
DATA_DENIED
SESSION_FAILED
SESSION_FAILED
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.
SESSION_EXPIRED
SESSION_EXPIRED
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.DATA_PUSH
DATA_PUSH
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 thedata array represents one financial account:| Field | Type | Description |
|---|---|---|
linkReferenceNumber | string | Unique reference for the linked account |
maskedAccountNumber | string | Masked account number |
fiType | string | Financial information type (e.g., DEPOSIT, MUTUAL_FUNDS, EQUITIES, RECURRING_DEPOSIT, TERM_DEPOSIT, ETF) |
bank | string | FIP/bank name |
Summary | object | Account summary with type-specific fields (balance, maturity, interest, etc.) |
Profile | object | Account holder profile information |
Transactions | object | Transaction history within the requested date range |
Integration Guidance
| Event | Recommended Action |
|---|---|
DATA_READY | Call Get FI Data or Get All FI Data to retrieve the financial data |
DATA_DENIED | Log the denial; check FIP status via FIP Health; notify the user if needed |
SESSION_FAILED | Retry with a new FI Request; check FIP Health if failures persist |
SESSION_EXPIRED | Submit a new FI Request if the consent is still active |
DATA_PUSH | Process the inline data array directly — no additional API calls needed |
