Get account statements.
The Fiskil Data Provider will include a self-signed JWT as a Bearer token in the Authorization header.
You should verify this JWT using the JWKS URL you can find for your Data Provider instance in the Fiskil
Console. To verify the JWT you must:
exp claimsub and iss claims are your data provider subdomainaud claim is the URI of the resource being requested (excluding any query parameters)jti value is unique
For further detail on security and authentication refer to our Authentication documentationUnique identifier for the user the account belongs to. This will be the user that authorized the data sharing.
Value for a unique identifier
256"someLongTermUniqueIDString"
Account identifier, found in the GET /accounts endpoint response.
Note: If the status of the accountId provided is RESTRICTED, you can send a 200 response with an empty body to indicate that no payment networks are available at this time.
Value for a unique identifier
256"someLongTermUniqueIDString"
An opaque ID that indicates there is at least one more page of data available. This value does not need to be numeric or have any specific pattern. If provided, the Data Provider will use this value to send a new request and retrieve the next page. Omitting this value indicates that there is no more data to retrieve.
"qwer123454q2f"
The number of elements that the API consumer wishes to receive. To retrieve multiple pages, the Data Provider will use the opaque nextOffset field to send a subsequent request until the nextOffset is no longer included.
Start time for use in retrieval of elements (ISO 8601). For transactions, this should filter by the postedTimestamp of the transaction
ISO 8601 full-date in format 'YYYY-MM-DD' according to IETF RFC3339
10"2021-07-15"
End time for use in retrieval of elements (ISO 8601). For transactions, this should to filter by the postedTimestamp of the transaction
ISO 8601 full-date in format 'YYYY-MM-DD' according to IETF RFC3339
10"2021-07-15"
Paginated list of available statements