Skip to main content
GET
List transactions
Read Transfers and transactions to understand how transfer instructions relate to account impacts.

Authorizations

X-API-Key
string
header
required

User API key authentication. Create a key under Settings → API keys in the Slash dashboard (https://app.slash.com/global-settings/api-keys) and send the x-legal-entity header naming the legal entity to act on with every request. Keys scoped to a legal entity are rejected with 403 user_api_key_required.

Headers

The legal entity to act on. Required on every request; a user API key can act on any legal entity its user has access to.

Pattern: ^le_[a-zA-Z0-9]+$

Query Parameters

cursor
string

Pass the opaque value returned in metadata.nextCursor without changing the other query parameters.

accountId
string

Return activity for one accessible Account.

virtualAccountId
string

Return transactions associated with one accessible virtual account. Transactions without a virtual-account association do not match.

category
enum<string>

Return transactions in one category. Category filter for listing transactions. other is not filterable; those transactions only appear in unfiltered lists.

Available options:
card,
ach,
wire,
international_wire,
realtime,
book,
fee,
check,
crypto,
treasury
status
enum<string>

Return transactions with this broad accounting status. Coarse transaction state.

Available options:
pending,
posted,
failed
detailedStatus
enum<string>

Return transactions in this exact lifecycle state. Must apply to the selected category when one is given. Exact transaction lifecycle state across every category.

Available options:
pending,
pending_destination,
pending_approval,
in_review,
scheduled,
canceled,
failed,
settled,
declined,
refund,
reversed,
returned,
dispute
transferId
string

Return the transactions produced by one transfer. Uses the transfer_intent_ prefix.

from
string<date-time>

Inclusive RFC 3339 lower bound on transaction date.

to
string<date-time>

Inclusive RFC 3339 upper bound on transaction date.

includeSummary
boolean
default:false

Include totals across the complete filtered result, not only this page.

Response

A page of transactions. Every item has the same core fields and identifies its category. Payment- or network-specific information appears under details.

items
(TransactionCard · object | TransactionAch · object | TransactionWire · object | TransactionInternationalWire · object | TransactionRealtime · object | TransactionBook · object | TransactionFee · object | TransactionCheck · object | TransactionCrypto · object | TransactionTreasury · object | TransactionOther · object)[]
required

Card activity with merchant and authorization data in details. This is the card variant of the unified Transaction model: category is always card and detailedStatus is limited to card lifecycle states.

metadata
PaginationMetadata · object
required
summary
TransactionSummary · object

Totals over every transaction matching the request's filters, not just the returned page. Present only when includeSummary=true.