Skip to main content
GET
Get a transaction

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

The ID of the transaction to retrieve.

Response

Successful operation

id
string
required

The unique identifier assigned by Push, prefixed with "txn_".

amount
integer
required

Amount of the transaction in the smallest currency unit (for USD, integer cents). Always non-negative — use direction to determine which way the money moved.

Required range: x >= 0
direction
enum<string>
required

Direction of the payment.

  • Submit cash_in for deposits
  • Submit cash_out for withdrawals
Available options:
cash_in,
cash_out
currency
enum<string>
required

Currency associated with the amount

Available options:
USD
status
enum<string>
required

The stage of the transaction in its settlement lifecycle. The set of stages a transaction moves through depends on its direction:

  • cash_in: pending → available → settled (available is cash_in only)
  • cash_out: pending → in_transfer → settled (in_transfer is cash_out only)
Available options:
pending,
available,
in_transfer,
settled
type
enum<string>
required

The type of activity that created the transaction.

Available options:
intent,
refund,
dispute
source_id
string | null
required

The ID of the intent, refund, or dispute that created this transaction. Read together with type to locate the source object.

account_id
string
required

The ID of the account the transaction settles against.

created_at
string<date-time>
required

When the transaction was recorded (ISO 8601 timestamp).

date
string<date>
required

The settlement window (the Eastern-time day) in which the transaction was submitted to Push. See the Ledger guide for how windows map to settlement dates.

transfer
object | null

The transfer that settles this transaction. Populated once the transaction reaches in_transfer or settled; null beforehand.

Example: