Skip to main content
GET
/
fdx
/
v6
/
customer
/
{customerId}
/
accounts
/
{accountId}
/
transactions
Search for account transactions
curl --request GET \
  --url https://your-company.com/fdx/v6/customer/{customerId}/accounts/{accountId}/transactions \
  --header 'Authorization: Bearer <token>'
{
  "page": {
    "nextOffset": "B47D80MVP23T"
  },
  "transactions": [
    {
      "accountCategory": "DEPOSIT_ACCOUNT",
      "transactionType": "CHECK",
      "checkNumber": 1234,
      "payee": "ACME LLC",
      "transactionId": "depositTransaction000000001",
      "postedTimestamp": "2022-04-06T00:00:00.000Z",
      "transactionTimestamp": "2022-04-05T00:00:00.000Z",
      "description": "check for latest ACME invoice",
      "debitCreditMemo": "DEBIT",
      "status": "PENDING",
      "amount": 400
    },
    {
      "accountCategory": "DEPOSIT_ACCOUNT",
      "transactionType": "ADJUSTMENT",
      "transactionId": "depositTransaction000000002",
      "postedTimestamp": "2022-04-07T00:00:00.000Z",
      "transactionTimestamp": "2022-04-07T00:00:00.000Z",
      "description": "reconciliation/adjustment of bank statement error",
      "debitCreditMemo": "DEBIT",
      "status": "POSTED",
      "amount": 0.8
    },
    {
      "accountCategory": "DEPOSIT_ACCOUNT",
      "transactionType": "ATMDEPOSIT",
      "transactionId": "depositTransaction000000003",
      "postedTimestamp": "2022-04-08T00:00:00.000Z",
      "transactionTimestamp": "2022-04-08T00:00:00.000Z",
      "description": "ATM cash deposit location #1234",
      "debitCreditMemo": "CREDIT",
      "status": "POSTED",
      "amount": 101.8
    }
  ]
}

Authorizations

​
Authorization
string
header
required

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:

  • Verify the signature
  • Ensure the token has not expired by checking the exp claim
  • The sub and iss claims are your data provider subdomain
  • The aud claim is the URI of the resource being requested (excluding any query parameters)
  • The jti value is unique For further detail on security and authentication refer to our Authentication documentation

Path Parameters

​
customerId
string
required

Unique identifier for the user the account belongs to. This will be the user that authorized the data sharing.

Value for a unique identifier

Maximum string length: 256
Example:

"someLongTermUniqueIDString"

​
accountId
string
required

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

Maximum string length: 256
Example:

"someLongTermUniqueIDString"

Query Parameters

​
offset
string

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.

Example:

"qwer123454q2f"

​
limit
integer

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.

​
startTime
string<date>

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

Maximum string length: 10
Example:

"2021-07-15"

​
endTime
string<date>

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

Maximum string length: 10
Example:

"2021-07-15"

Response

Paginated collection of transactions.

Base class for results that may be paginated

​
transactions
(Deposit Transaction · object | Investment Transaction · object | Line-Of-Credit Transaction · object | Loan Transaction · object)[]
required

An optionally paginated array of transactions. May be any of the following: deposit transaction, investment transaction, loan transaction, line of credit transaction

A transaction on a deposit account type

Example:
{
  "accountCategory": "DEPOSIT_ACCOUNT",
  "transactionId": "78RJ3311PLU34300E",
  "transactionTimestamp": "2024-07-15T14:46:41.375+02:00",
  "description": "ATM deposit",
  "debitCreditMemo": "DEBIT",
  "status": "PENDING",
  "amount": 38.9
}
​
page
Page Metadata · object

Contains the opaque identifier, nextOffset, to indicate a paginated result set.