ingestion
Per-block pipeline ingestion timings, measured at the source.
Raptor's own ingestion telemetry, one row per block: the pipeline commits a block as one or more flushes (micro-batches in transaction-streaming mode), and this view aggregates them per slot. These are the numbers behind the live latency badge on the market page. Roughly the last minute of blocks is available.
Try it
Sign in to run live
- Change wallet
Parameters
Maximum data points (1-300, default 60). Query only; ignored when streaming.
Request
curl -X POST https://rpc.raptor.trade \
-H "Authorization: Bearer $RAPTOR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "solana::market::ingestion",
"params": {
"limit": 10
}
}'Response
Responses are always a JSON array - one entry per request - and each entry's result holds the array of data. The shape is identical over HTTP and WebSocket.
[
{
"jsonrpc": "2.0",
"id": 1,
"result": [
{
"id": 1024,
"slot": "432305292",
"timestamp": "2026-06-01T02:16:22.000000000Z",
"started_at": "2026-06-01T02:16:22.113000000Z",
"took": "PT0.003841S",
"batches": "27",
"records": "214"
}
]
}
]Fields
Numbers come back as strings and timestamps as ISO-8601 strings; every data point carries a stable id. See Data model.
Solana slot (block) that was ingested.
Block time of the ingested block.
When the pipeline began processing the first flush of the block.
Slowest single flush of the block, receipt to queryable, measured in the pipeline.
Flushes committed for the block; more than one in transaction-streaming mode.
Total rows written for the block across all flushes.
Errors
Invalid parameters return -32602; an unknown method returns -32601. See Errors for the full table.
