Skip to main content
POST

Overview

Retrieves the canonical BlockDB representation of a single record, keyed by its lineage identifier. This is the lightweight entry point before requesting heavier parent expansions.

Parameters

number
required
EVM network identifier. See the Chain enumeration for supported values.
string
required
Lineage identifier for the target record (18-byte hex, exactly 36 characters, no 0x prefix). The legacy _tracing_id key is still accepted.

Response Fields

Meta

object
Echo of request metadata applied to the response.
number
EVM chain ID echoed from the request.
string
Tracing identifier for the record whose artifacts are returned.

Data

object | null
Envelope containing the record payload. null when no record matches the supplied tracing_id (the response is still 200 OK, not 404).
A lookup that finds no matching record returns 200 OK with "data": null (with meta still echoed), consistent with how list endpoints return an empty range. A 404/400 is only returned for malformed requests (missing chain_id, missing/short tracing_id, or an unknown dataset-id prefix).
string
Dataset namespace that owns the record (e.g., 0201_tokens-erc20).
object
Snapshot of the dataset-specific fields for this record. Binary columns (addresses, hashes, tracing ids) are returned as bare lowercase hex — no 0x and no Postgres \x prefix. Common metadata includes:
number
Network identifier copied from the envelope.
string
Dataset-specific primary key (illustrated here with a token contract address).
number
Canonical block height where the record last changed.
string
ISO-8601 timestamp for the block that produced the record state.
number
Transaction position for provenance auditing when applicable.
number
Log position for provenance auditing when applicable.
string
Internal variant of tracing_id (18-byte hex, exactly 36 characters).
string[]
Internal variant mirrored for completeness.
string
Internal created-at timestamp.
string
Internal updated-at timestamp.
  • name, symbol, decimals
    Dataset fields shown for the ERC-20 example. Actual shape varies per dataset—consult the dataset’s schema docs.

Next Steps

Last modified on July 19, 2026