GET /api/v1/anchors
Retrieve a list of blockchain anchors for your workspace, ordered by creation date (newest first). Each anchor represents a Merkle root computed from events in a given period and submitted to the Base blockchain.Query Parameters
Number of anchors to return (max 100).
Response
Response Fields
| Field | Type | Description |
|---|---|---|
id | string | Unique anchor identifier |
merkle_root | string | 64-character hex SHA-256 Merkle root of events in this period |
previous_anchor_hash | string | null | SHA-256 hash of the previous anchor’s merkle_root + tx_hash. Null for the first anchor |
events_count | integer | Number of events included in the Merkle tree |
period_start | string | ISO 8601 start of the anchoring period |
period_end | string | ISO 8601 end of the anchoring period |
chain | string | Blockchain network (base) |
status | string | pending, submitted, or confirmed |
tx_hash | string | null | Blockchain transaction hash. Null if not yet submitted |
block_number | integer | null | Block number of the confirmed transaction. Null if not yet confirmed |
explorer_url | string | null | Direct link to the transaction on Basescan |
created_at | string | ISO 8601 timestamp of anchor creation |
Examples
Anchors with
status: "pending" or status: "submitted" will have null values for tx_hash, block_number, and explorer_url. These anchors cannot yet be verified on-chain.