List all transactions across the partner's accounts
GET/api/partner/transactions
Returns every transaction the authenticated partner is allowed to see, aggregated across all of its linked individual onboardings (and any B2B-shared tenant accounts that those onboardings resolve to).
This endpoint is paginated. The default is page=1 and limit=10.
There is currently no hard server-side cap on limit.
Pass the values as query parameters, for example
?page=2&limit=3000. The response contains the transaction data
and pagination metadata including the total number of matching
rows and total pages.
Filter rules. The two filters are mutually exclusive — passing both at once returns 400:
?accountIdentification=…— narrow to one or more IBANs. Accepts a single IBAN, a comma-separated list (?accountIdentification=DE1,DE2), or repeated keys (?accountIdentification=DE1&accountIdentification=DE2). Any IBAN the partner does not own is silently excluded from the result. If every supplied IBAN is foreign to the partner, the endpoint returns 404 "IBAN not found."?cardId=<cardKey>— narrow to a single card. Exactly one cardKey is allowed; passing multiple (repeated keys or comma-separated) returns 400. An unowned cardKey returns 404 "Card not found!".
When neither filter is supplied, the partner's full owned-IBAN union is queried. If the partner has zero owned IBANs the endpoint returns 400.
Empty result sets (no rows in the date range) are returned with
HTTP 200 and an empty data array — mirroring
/individual/accounts/{id}/transactions.
Request
Responses
- 200
- 400
- 401
- 404
Transactions
Bad request — typically because both accountIdentification
and cardId were supplied, or because multiple distinct
cardId values were supplied.
Unauthorized — missing or invalid JWT
Not found — every supplied accountIdentification is foreign
to the partner, or the supplied cardId is foreign (or
unknown). The endpoint never reveals whether the resource
exists in another partner's scope.