Returns a list of all transactions under the account.
By default, GET /transactions returns transactions ordered by the latest createdAt. You can combine the different filters as documented.
This endpoint supports cursor-based pagination.
Add expand to embed each transaction's related resources under _embedded in the same response, for example expand=cardSubscription,card,cardholder. Each embedded resource is the exact body its own endpoint serves, shows its current values (not those at the time of the transaction) except cardholder.corporate, which is resolved as of the transaction's date (see the expand parameter), and requires that endpoint's scope: card-subscriptions:read for cardSubscription, cards:read for card, cardholder:read for cardholder. Transactions without a given related resource simply omit that key. Pagination links preserve expand.
For the company and legal entity a card belonged to when the transaction happened, use expand=cardholder and read cardholder.corporate.id and cardholder.corporate.legalEntity. They are the values in effect on the transaction's transactionOccurrenceDate (through the end of that UTC day), or at the transaction's createdAt when that is null, so a card that later moved to another company or legal entity keeps its historical attribution on past transactions. Transactions themselves do not carry a company identifier.
To list the transactions of one company or legal entity, filter with companyId, legalEntityId or legalEntityName. They match the cardholder's corporate.id, corporate.legalEntity.id and corporate.legalEntity.name on the transaction date: the values expand=cardholder returns on each transaction, not the cardholder's current ones (see the Glossary). Each is an exact, case-sensitive match, so copy the value from a transaction's expand=cardholder. The filters use the same as-of resolution as expand=cardholder, including the earliest recorded values for a transaction dated before Astrada started recording the card's corporate history. A transaction whose card has no cardholder data, or whose card GET /cards/{cardId} no longer returns, does not match, just as expand embeds no cardholder for it. They combine with each other and with transactionMessageId, cardId, subaccountId and networkBulkFeedId: supplying more than one returns only the transactions matching all of them. Transactions without a card never match. For example, this returns one legal entity's transactions on one feed:
GET /transactions?networkBulkFeedId=<feed>&legalEntityId=<id>
URL-encode the values. In legalEntityName a space is %20 (or +), and a literal + is read as a space, so send a + in the name as %2B. Send each filter once. Leading and trailing spaces are ignored. A value that is empty or only spaces, or longer than 255 characters, is refused with 400.
With any of these filters a page can hold fewer than limit transactions, even none, while _links.next is present. Keep following _links.next until it is absent.
These three filters read cardholder data, so they need the cardholder:read scope, like expand=cardholder. Without it the request returns 403.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
