Quickstart
1
Get Access
Parsed Events is available on all plans at 10 credits per request. Get your API key from the Helius Dashboard and send requests to
https://mainnet.helius-rpc.com.Authenticate with your project’s API key, passed as the api-key query parameter.2
Parse a Transaction
Pass signatures in the
transactions body field of POST /v1/parsed-events/transactions:- JavaScript
- cURL
3
Read the Result
The response contains one result per requested signature, in input order. Each result includes The example is trimmed to two instructions: a decoded token transfer inside the route, and an AMM instruction whose program the catalog knows but cannot decode, which leaves
signature, parserStatus, and either parsed or parserError:instructionName as null while rawData and rawAccounts remain available. See Parsed Response for every field and a full example response.4
Fetch Address History
POST /v1/parsed-events/transaction-history returns the same parsed results as above, for every transaction that touched an address, newest first by default:- JavaScript
- cURL
5
Paginate
History responses wrap results in a page object. Pass
paginationToken back in the next request to continue. If paginationToken is missing, the service reached the end of the available page range.Guides
Fetch Pump.fun Mints
Page through every token a wallet has deployed on Pump.fun.
Migrate from Enhanced Transactions
Endpoint, parameter, and response mapping from the legacy API.
REST Reference
Both REST methods accept a JSON body viaPOST under /v1/parsed-events/ at https://mainnet.helius-rpc.com, authenticated with the api-key query parameter. Request bodies reject unknown fields, so typos fail loudly instead of being silently ignored.
Parse Transactions
POST /v1/parsed-events/transactions fetches full Solana transactions by signature, decodes them with the same IDL-based instruction decoder that powers Parsed Streams, and returns one TransactionResult per requested signature.
The response order matches the input order, including duplicate signatures. Missing transactions and per-item parser failures are returned as item-level parserStatus: "ERROR" results:
Request body
Encoding of the raw Solana transaction returned as
rawTransaction on each result, in the getTransaction shape.nonejsonjsonParsedbase64
Notes
processedcommitment is not supported.rawTransactionis omitted unless you set therawTransactionrequest field tojson,jsonParsed, orbase64. The olderincludeRawTransaction: truestill works as an alias forjson.- Transaction execution failures can still parse. In that case
parsed.transactionStatusisERROR, and the transaction error is exposed onparsed.errorwhen available. - Request-level validation errors return an error response instead of item-level results.
Parsed Transaction History
POST /v1/parsed-events/transaction-history returns parsed transaction history for an address. It supports pagination, signature bounds, slot bounds, block-time bounds, sort order, and optional raw transactions.
Unlike the legacy Enhanced Transactions address endpoint, request parameters are sent in a JSON body rather than query string parameters.
Request body
Whether to include transactions that reference only a token account owned by
address, not address itself. Many incoming token transfers touch only the recipient’s token account.nonebalanceChangedall
Encoding of the raw Solana transaction returned as
rawTransaction on each result, in the getTransaction shape.nonejsonjsonParsedbase64
Pagination
Responses have this shape. Eachdata item uses the same TransactionResult format returned by Parse Transactions:
paginationToken back in the next request to continue. If paginationToken is missing, the service reached the end of the available page range.