Streaming

Parsed Streams

Receive decoded transaction notifications that match your program and account filters.

Try a short live stream

Open Parsed Streams, load your Relay key and add a program or account filter. Start stream opens the connection. The preview stops after 10 events or 30 seconds by default; you can choose up to 100 events and 60 seconds.

The preview also stops when you change keys, leave the page, or hide the tab. It does not start or reconnect automatically. No results can simply mean that no transaction matched during the preview.

Connect with your Relay key

Use the endpoint shown in your console. Parsed Streams requires an enabled service and positive WebSocket connection and subscription allowances in your active paid period. It shares these limits with your other WebSocket connections.

Parsed Streams connection

wss://relayrpc.top/parsed-streams?api-key=YOUR_RELAY_KEY

Replace the placeholder with your Relay key. Keep URLs containing credentials out of public code, screenshots and logs.

Subscribe with filters

Follow decoded Jupiter instructions

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "parsedTransactionSubscribe",
  "params": [
    {
      "programs": [
        "JUP6LkbZbjS1jKKwapdHNy74zcZ3tLUZoi5QNyVTaV4"
      ]
    },
    {
      "commitment": "confirmed",
      "details": "full"
    }
  ]
}

Field	Relay limit
`programs`	Up to 10 program addresses
`accounts.include`	Up to 100 account addresses
`instructionNames`	Up to 50 decoded instruction names, each up to 64 characters
`accounts.roles`	Up to 20 role-name/address pairs; role names up to 64 characters
`includeFailed`	Boolean; include instructions from failed transactions
`includeCpi`	Boolean; include inner instructions

Include at least one program or account. Values within a list are alternatives; supplied filter types combine together. Role filters map decoded role names to addresses, and every supplied role must match.

The console editor accepts programs, accounts and instruction names. It requests commitment: "confirmed" and details: "full". Your application can also send the role and boolean filters above.

Option	Accepted values
`commitment`	confirmed
`details`	full, matched, raw

full includes transaction context and matching instruction indexes. matched returns only matching instructions. raw returns instruction positions, program IDs and encoded data without decoded instruction fields. describeProgram is not exposed through Relay.

Read notifications and stop

The request ID identifies the subscription acknowledgement. Matching transactions arrive as parsedTransactionNotification messages. An acknowledgement is not an event and does not belong in your transaction results.

Close the connection when you finish. Use the Helius notification reference to interpret decoded transaction details and matching instruction indexes.

Credits and reservations

Parsed Streams costs 1 credit per matching notification received by Relay. Credits are reserved while connected; final usage appears after the stream closes. The initial reservation is 200 credits and is separate from recorded spending.

A browser event limit controls how many events the preview displays. Notifications already in flight may also count toward usage. Open Usage and choose Parsed Streams to inspect received events, credits and reservations.