GraphQL Interface

The Parsed Events GraphQL interface exposes both methods while letting clients select exactly the fields they need. Use transactions for Parse Transactions and transactionsByAddress for Parsed Transaction History.

Queries

`transactions`

Parse Transactions: parse one or more transaction signatures.

Argument	Type	Default	Description
`signatures`	`[String!]!`	-	Transaction signatures to parse.
`commitment`	`Commitment`	`CONFIRMED`	`CONFIRMED` or `FINALIZED`.

`transactionsByAddress`

Parsed Transaction History: fetch parsed transaction history for an address.

Argument	Type	Default	Description
`address`	`String!`	-	Address whose transaction history should be fetched.
`limit`	`Int`	`100`	Number of transactions to return.
`beforeSignature`	`String`	-	Return transactions before this signature.
`afterSignature`	`String`	-	Return transactions after this signature.
`paginationToken`	`String`	-	Cursor with shape `slot:transactionIndex`.
`sortOrder`	`SortOrder`	`DESC`	`ASC` or `DESC`.
`commitment`	`Commitment`	`CONFIRMED`	`CONFIRMED` or `FINALIZED`.
`filters`	`AddressTransactionFiltersInput`	-	Optional `slot` and `time` bounds.

Raw transaction selection

GraphQL includes rawTransaction only when selected in the query. If it is not selected, raw transaction payloads are omitted.

Error behavior

Request-level errors use GraphQL errors with an extension code such as BAD_REQUEST, NOT_FOUND, SERVICE_UNAVAILABLE, or INTERNAL_SERVER_ERROR. Per-item parser failures are returned in the data payload as parserStatus: ERROR with parserError.

API Reference

Solana RPC APIs

Solana APIs

Data Streaming APIs

Event Listening APIs

Account Management APIs

Queries

`transactions`

`transactionsByAddress`

Raw transaction selection

Error behavior

​Queries

​transactions

​transactionsByAddress

​Raw transaction selection

​Error behavior

Queries

`transactions`

`transactionsByAddress`

Raw transaction selection

Error behavior