The card account ID returned from the Get Card Accounts call.

The customer type for the request.

• PERSONAL: personal card accounts
• BUSINESS: business card accounts
• CORPORATE: corporate card accounts

Furthest date in the past of the requested transaction range. YYYY-MM-DD.
Recommended range is 1 year as some banks return a maximum of one year of transactions per request.
Split the date range across multiple requests to retrieve transactions spanning more than a year.

Most recent date of the requested transaction range. YYYY-MM-DD.

Cursor for pagination. When more transactions are available, the response includes a links array
with a link where rel is "next". Extract the cursor query parameter from the href URL and
pass it here to fetch the next page.

Example: If the response contains:

"links": [{ "rel": "next", "href": "https://sandbox.neonomics.io/.../transactions?cursor=0X4lQV7dZZ4x..." }]

Use cursor=0X4lQV7dZZ4x... in your next request.

Important:

• Do not pass fromDate and toDate when using cursor.
• The cursor is an encrypted opaque string — do not attempt to decode or modify it.

Filter transactions by booking status. By default all transactions are returned.

The session Id returned in the response body when this session was created.

String that uniquely identifies a single end-user or device.

The IP Address of the end-user (PSU), which must be provided if the PSU actively requests information.
If this value is not provided, then the call will count towards the number of TPP calls without PSU interaction.
Leave it empty if the end user is not actively requesting account information, such as during automatic background updates.
Provided in either IPv4 or IPv6 format.

Identifier of the end-user, passed as the base64-encoded value of an encrypted string following
the guidelines given in Documentation > Development > Sensitive end-user data.
This parameter is required if the value of 'personalIdentificationRequired' returned from the /banks endpoint is "true".

The host where the request is originating from.
If you are using end to end encryption from our developer portal then this header is mandatory.

The request originating date.
If you are using end to end encryption from our developer portal then this header is mandatory.

The signature header consisting of the signature string
If you are using end to end encryption from our developer portal then this header is mandatory.