Create a transactions request

The /v3/connected-accounts/{account\_id}/transactions/requests endpoint creates an asynchronous request to retrieve all the transactions for a specific account over a date range that you specify.

Note that you will not get a list of transactions in the initial response to this request. A 202 response returns the request id and an initial status of pending. You can then poll for the result using the returned id, using the GET endpoint.

Results are paginated and returned in a stable order: by booking date (timestamp) descending, then transaction_id descending as a unique tie-breaker. Make another request and pass the next_cursor from a previous page as cursor to retrieve the next page; an empty items array means there are no further transactions.

Authentication

You will need the following headers to create a transactions request:

A client credentials access token with the data scope
A Connection-Id with the transactions scope

You may also want to provide the IP address of the end user as a header. This confirms that your user is present when the request is made, enabling you to bypass rate limiting.

Build a create transactions request

Below are the parameters to include in a create transactions request.

Parameter	Required?	Format
`from`	Yes	string	The start of the date range (inclusive) for which to retrieve transactions, in YYYY-MM-DD format.
`to`	Yes	string	The end of the date range (inclusive) for which to retrieve transactions, in YYYY-MM-DD format.
`cursor`	No	string	Cursor used for pagination. Pass the next_cursor value from a previous GET transaction response to retrieve the next page of results.
`page_size`	No	number	The maximum number of transactions to return per page. Optional; if omitted, the maximum of 500 is applied and you receive the minimum possible (500, requested) items.

Below is an example request:

{
"from": "2025-04-01",
"to": "2026-04-01",
"cursor": "bWFuZGF0ZXM6MmUwNDk0MTMK",
"page_size": 100
}

Create transactions response

In an initial response, you receive:

an id for this transactions request
a status for the request, which will initially be pending

{
"id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"status": "pending"
}

You can then use the GET transactions endpoint to track the status of the request and see the full list of transactions, if the request is successful.