Data sources

Read the chain yourself, or use the HEX API, which indexes hexbook.near and serves history, a live stream, stats and charts.

From the chain

hexbook.near receipts come from:

Receipt	From	Carries
`mt_on_transfer`	`intents.near` (`mt_transfer_call` or a `transfer` intent)	orders, deposits
`on_auth`	`intents.near` (`auth_call` intent)	`batch`, `cancel_all`, `close_order`, `withdraw`, `claim_balance`, `set_payout_mode`
direct calls	any account / managers	`prune`; `create_order_book`, `set_protocol_fee`, `set_min_order_amount`, `set_tick_size`, `owner_close_order`, `emit_book_events`
`on_payout`	the book itself	the callback of each payout `mt_transfer`; logs `payout_failed` when it failed

Events are in the logs of hexbook.near’s own successful receipts. Ignore intents.near receipts: their mt_transfer events duplicate the token movements.

FastNEAR

FastNEAR indexes transactions by account:

# transactions that touched the book, ascending from a block height, paged with resume_token
curl -s https://tx.main.fastnear.com/v0/account -H 'content-type: application/json' \
  -d '{"account_id":"hexbook.near","from_tx_block_height":170000000,"limit":200,"desc":false}'
# → { "account_txs": [{ "transaction_hash", "tx_block_height", "tx_block_timestamp", ... }], "resume_token": "..." | null }

# receipts and logs of up to 20 transactions
curl -s https://tx.main.fastnear.com/v0/transactions -H 'content-type: application/json' \
  -d '{"tx_hashes":["CDr3zJNjLr786xXX2UZNJfaZvRvP29EvT8UE2Z5RJ8YA"]}'

Keyless access has lower rate limits (a long backfill meets HTTP 429); an API key goes in authorization: Bearer <key>. desc: true pages newest first. Full request shape: FastNEAR’s OpenAPI (docs.fastnear.com/openapi/transactions.json).

NEAR RPC

Without an index, use a NEAR archival RPC:

EXPERIMENTAL_tx_status { tx_hash, sender_account_id, wait_until: "FINAL" } returns every receipt outcome with its logs;
or follow blocks (block, chunk) and keep receipts with receiver_id == "hexbook.near", then EXPERIMENTAL_receipt / the transaction outcome for their logs;
or a NEAR Lake / streamer framework filtered on hexbook.near.

Views (get_orderbook, get_active_pairs, get_quote_pub, get_user_balance) go to any RPC with call_function.

The HEX API

Base URL: https://hex-api.app/orderbook. :contract is hexbook.near (or orderbook.fi.tg, HOT’s book). Token ids are URL-encoded. It is meant for server-side use: browser requests from other origins are rejected (CORS). Rate limits per IP: 300 reads and 30 POST /tx per minute.

Route	Answer
`GET /v1/health`	each book’s forward cursor, backfill state, row count and newest row time
`GET /v1/:contract/transactions?base_token&quote_token[&account_id][&tx_hash]`	`{ transactions }`, newest first, at most 500
`GET /v1/:contract/events[?after=<id>][&base_token&quote_token][&limit]`	`{ events, last_id }`: rows after `after`, oldest first; without `after`, none and the newest id
`GET /v1/:contract/stream[?base_token&quote_token][&after][&wait=0..25]`	Server-Sent Events of the same rows (`data: {type, id, contract, base_token, quote_token, near_trx, transaction}`); reconnect with `Last-Event-ID`
`GET /v1/:contract/stat?base_token&quote_token`	`{ volume_ask_30d, volume_bid_30d, volume_ask, volume_bid, best_ask, best_bid, last_price, trades_24h }`
`GET /v1/:contract/chart?base_token&quote_token&step=0..3[&only_sell=true\|&only_buy=true][&include_volume=true]`	`{ chart, volume_chart }` from the book’s own trades
`GET /v1/:contract/referrals?account_id`	referral earnings of an account
`GET /v1/:contract/orders?account_id[&base_token&quote_token][&status=open\|closed\|all][&limit]`	`{ orders }`: an account’s orders with status, close reason, refund, remaining amount, expiry, epoch and `dead` (`expired` / `epoch`) for open orders that can no longer trade
`GET /v1/:contract/activity?account_id[&limit]`	`{ activity }`: deposits, claims, failed payouts, maker fills (with `internal`), skipped placements, epoch bumps and payout-mode changes
`POST /v1/:contract/tx` `{ "tx_hash": "..." }`	index one transaction now: 200 `{ found: true, events, … }`, 202 when FastNEAR does not have it yet

Rows are history entries (order_created, order_closed, market_swap) normalized for display, not raw contract events. They do not carry deposits, skips, epochs, payout modes or internal-balance credits: for those, and for exact settlement, index the contract logs yourself. Latency: the HEX API syncs every ~10 s plus FastNEAR’s lag; POST /tx right after your transaction makes it visible at once.

Example: follow your fills

let after = (await (await fetch(`${API}/v1/hexbook.near/events`)).json()).last_id;
setInterval(async () => {
  const url = `${API}/v1/hexbook.near/events?after=${after}&base_token=${encodeURIComponent(BASE)}&quote_token=${encodeURIComponent(QUOTE)}`;
  const { events, last_id } = await (await fetch(url)).json();
  for (const row of events) handle(row); // filter rows where you are the maker
  after = last_id ?? after;
}, 5_000);

Backfill strategy

Snapshot first

Read get_active_pairs, then get_orders({ token_pair, skip, limit }) per book (pages of 100–200). This gives every resting order (dead ones included; see get_order_meta) with its maker, side, price, created_ts and balance.

Place the forward cursor

Remember the snapshot’s block height and follow new transactions from there (FastNEAR /v0/account ascending from the cursor minus ~60 blocks, or a block stream).

Backfill history backwards

Page /v0/account newest first from the cursor down to the book’s first transaction. Make the backfill idempotent.

Key rows idempotently

Use {receipt id}:{log index} as the unique key of an event so the overlap of forward sync, backfill and on-demand indexing stores nothing twice.

Handle out-of-order reads

A backfill that goes newest first reads an order_closed or a fill before its order_created. Store the hash and fill in maker, side and price once the order is read (or from get_order while it is still open).

Overview

Contract

Market making

Indexing

From the chain

FastNEAR

NEAR RPC

The HEX API

Example: follow your fills

Backfill strategy

​From the chain

​FastNEAR

​NEAR RPC

​The HEX API

​Example: follow your fills

​Backfill strategy

From the chain

FastNEAR

NEAR RPC

The HEX API

Example: follow your fills

Backfill strategy