Skip to main content

Transaction result envelope

REST endpoints return TransactionResult objects. GraphQL exposes the same fields as typed objects.

Parsed transaction

Native transfers

nativeTransfers contain SOL movements in lamports. Native transfers include System Program transfer and create_account instructions, plus synthetic SPL Token close_account SOL transfers.

Token transfers

tokenTransfers contain SPL Token and Token-2022 movements. Token transfers include transfer, transfer_checked, transfer_checked_with_fee, burn, burn_checked, mint_to, and mint_to_checked. Zero-amount token transfers are omitted.

Summaries

summary has one shape everywhere it appears — on the transaction and on each recognized instruction:
parsedData is the structured payload behind the summary, when available — for example swap metadata with the protocol, kind, amounts, mints, and any inner swaps along the route. Its shape varies by summary type and protocol. Current summary types include:
  • add_liquidity
  • create_account
  • create_token_account
  • remove_liquidity
  • swap
  • transfer

Parsed instructions

Decoded instruction accounts have this shape:
Decoded args keys and account names are snake_case (source_account, in_amount), as published in the program’s IDL. Integer arguments are commonly returned as strings ("1500000000000") because u64 values do not fit in JavaScript numbers.

Decoded errors

When a transaction fails with a custom program error and the API can identify the failing program error, decodedError can include:

Full example

A complete Parse Transactions result for a Jupiter SOL-to-PUMP swap, showing the envelope, transfers, summaries, and every instruction: