Skip to main content
GET
Retrieve a card transaction

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]+$

Path Parameters

transactionId
string
required

Transaction id with the agg_tx_ prefix.

Response

The card transaction.

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.

id
string
required

Transaction id.

Example:

"agg_tx_2rj4l7hmrrrcv"

date
string<date-time>
required

Posting date, or creation date while pending or failed.

Example:

"2026-08-18T01:00:00.000Z"

description
string
required

Statement descriptor when one was supplied; otherwise a Slash-generated display description.

Example:

"VENDOR PAYMENT"

amountCents
integer
required

Signed USD account impact in cents. Debits are negative.

Example:

-1250

status
enum<string>
required

Coarse transaction state.

Available options:
pending,
posted,
failed
accountId
string
required

Account containing the transaction.

Example:

"sa_group_primary123"

accountSubtype
enum<string>
required

Balance type affected by the transaction.

Available options:
cash,
credit
Example:

"cash"

category
enum<string>
required
Available options:
card
detailedStatus
enum<string>
required

Exact lifecycle state of a card transaction.

Available options:
pending,
canceled,
failed,
settled,
declined,
refund,
reversed,
dispute
memo
string

Human-readable payment memo, when present. For transfers, this is the request's top-level description.

Example:

"Invoice 1042"

note
string

User-editable private note, when present.

Example:

"Reconciled with invoice 1042"

virtualAccountId
string

Virtual account containing the transaction, when applicable.

Example:

"subaccount_operations123"

transferId
string

The transfer that produced this transaction, if any. Uses the transfer_intent_ prefix.

Example:

"transfer_intent_2rj4l7hmrrrcv"

originalCurrency
object

Original currency details when the transaction was converted. Despite the historical amountCents field name, the amount uses the original currency's native minor unit.

details
object

Card, merchant, and authorization data for a card transaction.