Portal API introduction - SQD Documentation

SQD Portal is an HTTP API for querying blockchain data. A Portal endpoint exposes one or more datasets. Each dataset identifies a chain or another named data source, such as ethereum-mainnet. A stream request has two parts:

The URL selects the dataset and operation.
The JSON body selects the request type, block range, fields, and filters.

For example, an EVM stream request can use this path:

POST /datasets/ethereum-mainnet/stream

Its request body includes type: "evm", a required fromBlock, an optional toBlock, and the fields or records to return. Solana requests use the same URL structure with the Solana request model. Stream response bodies use JSON Lines. Each line is one JSON object for one returned block. A client can read and process each line as it arrives. Do not select the parser from the Content-Type header alone. The SQD-hosted endpoint can use different content types for archival and recent data while returning the same line-delimited JSON body.

How Portal serves data

See how one stream can read finalized history and recent blocks.

Finalized and recent data

Choose between standard and finalized streams.

Blockchain forks

Detect a changed chain and recover from HTTP 409.

First query

Choose a runnable query for EVM, Solana, Bitcoin, Hyperliquid, Tron, or Substrate data.

The pages in this section explain the shared API concepts. The first-query selector links to the existing runnable requests, request fields, filters, and response examples for these data types. To operate a Portal instance, see Running your own Portal.