Retrieve transaction data
Get historical transactions list:
curl https://b2b.revolut.com/api/1.0/transactions \
-H "Authorization: Bearer <your access token>"
Example response:
[
{
"id": "602ee3c3-67s4-ac64-baec-6ede391ba9b5",
"type": "fee",
"state": "completed",
"created_at": "2021-02-18T22:01:39.223762Z",
"updated_at": "2021-02-18T22:01:39.223762Z",
"completed_at": "2021-02-18T22:01:39.223930Z",
"legs":
[
{
"leg_id": "2fe2f7fa-7a81-4722-8c0e-88e1b788250f",
"account_id": "041c7846-4c5e-44af-b8f6-206f61e9f60a",
"amount": -7,
"currency": "GBP",
"description": "Freelance Pro plan fee",
"balance": 11.37
}
]
},
{
"id": "6ebc74ed-01db-4a56-b555-d5d0be6938de",
"type": "transfer",
"state": "completed",
"request_id": "f5c2d005-f10c-4d19-9d97-01b3746b365b",
"created_at": "2021-02-11T12:02:37.286562Z",
"updated_at": "2021-02-11T12:02:40.207817Z",
"completed_at": "2021-02-11T12:02:40.201404Z",
"reference": "Test",
"legs":
[
{
"leg_id": "e1dc29a0-41e0-4cd0-a6a4-2014fe6903f3",
"account_id": "a50d90ef-dd4a-4167-938b-03737c9af50f",
"counterparty":
{
"id": "95fde753-5dd3-4e3b-895b-5345f4f1e86d",
"account_type": "external",
"account_id": "ad598215-5997-4d8e-a65f-0b992842c2cd"
},
"amount": -0.01,
"currency": "EUR",
"description": "To John Smith",
"balance": 0
}
]
}
]
Learn how to retrieve the historical transactions based on the provided query criteria.
The API returns a maximum of 1,000 transactions per request.
To be compliant with PSD2 SCA regulations, we only allow access to the last 90 days' transactions.
However, you can access older transactions within the first 5 minutes of an account access token being authorized. This means that within the first 5 minutes of a Revolut user authenticating your request, you can request data older than 90 days. After the 5 minute mark, the access to the transaction data is automatically restricted only to the last 90 days.
Filter transactions
Get a filtered transaction list:
curl https://b2b.revolut.com/api/1.0/transactions? \
counterparty=5138z40d1-05bb-49c0-b130-75e8cf2f7693 \
&from=2017-06-01 \
&to=2017-06-10 \
&count=10 \
&account=041c7846-4c5e-44af-b8f6-206f61e9f60a \
-H "Authorization: Bearer <your access token>"
You can filter the transactions returned by adding one or more of the following parameters to the URL.
The following table lists the parameters that you can optionally add as filters:
| Parameter | Description | Required | Schema |
|---|---|---|---|
from | The date and time you retrieve the historical transactions from. | No | ISO date/time |
to | The date and time you retrieve the historical transactions to. The default value is now. | No | ISO date/time |
counterparty | The ID of the counterparty. | No | UUID |
account | The account ID. | No | UUID |
count | The number of the historical transactions to retrieve. The maximum number is 1,000. The default number is 100. | No | Number |
type | The type of the historical transactions to retrieve, which can be atm, card_payment, card_refund, card_chargeback, card_credit, exchange, transfer, loan, fee, refund, topup, topup_return, tax, or tax_refund. | No | Text |
Pagination of transactions
The /transactions endpoint supports time-based pagination. It returns transactions in reverse chronological order (from <= created_at < to) limited to most recent count entities. Thus, to get the next page of results, you should set parameter to with the value of created_at last item of the previous page.