> ## Documentation Index
> Fetch the complete documentation index at: https://www.helius.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Parsed Events

> Parse Solana transactions and address history into decoded instructions, transfers, and summaries over REST or GraphQL.

<Note>
  Parsed Events is in **closed beta**. Access is enabled per project for now, and the API may change before general availability. To join the closed beta, [apply here](https://form.typeform.com/to/BlFWKbC9).
</Note>

## What is Parsed Events?

Parsed Events returns parsed Solana transaction data from raw transaction signatures or address history. It exposes the same parsed transaction model through REST JSON and GraphQL.

Instructions are decoded through the same IDL catalog that powers [Parsed Streams](/docs/parsed-streams): named instruction arguments, named accounts, and inner (CPI) instructions. Parsed Streams pushes matching transactions to you in real time over WebSocket; Parsed Events parses signatures and address history on demand. If the decoding model is new to you, read the Parsed Streams [mental model](/docs/parsed-streams#the-mental-model) first.

Parsed data includes:

* decoded instruction names, accounts, and arguments;
* transaction and instruction summaries;
* native SOL transfers;
* SPL Token and Token-2022 transfers;
* structured summary data (`parsedData`) for supported protocols;
* decoded custom program errors when program metadata is available;
* the original raw transaction payload when requested.

## Methods

Parsed Events has two methods. Both are available through REST and GraphQL.

| Method                     | REST                        | GraphQL                 | Description                                      |
| -------------------------- | --------------------------- | ----------------------- | ------------------------------------------------ |
| Parse Transactions         | `POST /transactions`        | `transactions`          | Parse one or more transaction signatures.        |
| Parsed Transaction History | `POST /transaction-history` | `transactionsByAddress` | Fetch parsed transaction history for an address. |

### How it compares

<CardGroup cols={2}>
  <Card title="vs Parsed Streams" icon="tower-broadcast">
    [Parsed Streams](/docs/parsed-streams) pushes decoded transactions over WebSocket as they land, filtered server-side at the instruction level. Parsed Events parses signatures and address history on demand over REST and GraphQL.
  </Card>

  <Card title="vs Enhanced Transactions" icon="clock-rotate-left">
    [Enhanced Transactions](/docs/enhanced-transactions/overview) is the previous-generation parse and history API built on fixed event types. Parsed Events decodes instructions through the IDL catalog into named arguments and accounts.
  </Card>
</CardGroup>

## Access

Parsed Events is enabled per project during the closed beta. The Helius team shares the API endpoint with you when your project is enabled.

Authenticate with your project's API key, passed as the `api-key` query parameter.

## Get Started

<CardGroup cols={2}>
  <Card title="Quickstart" icon="bolt" href="/docs/parsed-events/quickstart">
    Parse your first transaction, fetch address history, and page through results.
  </Card>

  <Card title="Fetch Pump.fun Mints" icon="rocket" href="/docs/parsed-events/guides/fetch-pumpfun-mints">
    Page through every token a wallet has deployed on Pump.fun.
  </Card>

  <Card title="Query with GraphQL" icon="diagram-project" href="/docs/parsed-events/guides/query-with-graphql">
    Select exactly the parsed fields your app needs.
  </Card>

  <Card title="Parsed Response" icon="brackets-curly" href="/docs/parsed-events/parsed-response">
    Field reference for parsed transactions, transfers, and instructions.
  </Card>
</CardGroup>