Skip to content
Fordnet

Developers

Fordnet REST API v1

Public Zcash chain data as JSON. Free keys, 200 requests/day each.

Quick start

  1. Generate a key below. It's shown once; we store only its SHA-256 hash.
  2. Send it in the x-api-key header.
  3. Every response is { data, meta, error }. Errors set data: null and a readable error.message.

Get an API key

curl examples

export FORDNET_KEY=fn_your_key_here
curl -s -H "x-api-key: $FORDNET_KEY" https://fordnet.vercel.app/api/v1/network/status
curl -s -H "x-api-key: $FORDNET_KEY" "https://fordnet.vercel.app/api/v1/blocks?limit=5"
curl -s -H "x-api-key: $FORDNET_KEY" https://fordnet.vercel.app/api/v1/blocks/2500000
curl -s -H "x-api-key: $FORDNET_KEY" "https://fordnet.vercel.app/api/v1/pools/history?range=7d"

Endpoint reference

  • GET/api/v1/network/status

    Sync state, height, hashrate, difficulty, last block, pool values.

    Params: —

  • GET/api/v1/blocks?limit=20

    Most recent blocks, newest first.

    Params: limit 1–50 (default 20)

  • GET/api/v1/blocks/{heightOrHash}

    One block with per-tx public summaries.

    Params: height (int) or 64-hex hash

  • GET/api/v1/tx/{txid}

    Public fields of a transaction; shielded parts as counts only.

    Params: 64-hex txid

  • GET/api/v1/address/{taddr}

    Transparent balance + recent transparent txs.

    Params: t1… or t3… address

  • GET/api/v1/pools/history?range=30d

    Daily value-pool snapshots (ZEC).

    Params: range 7d | 30d | all

Errors, limits & caching

400
— invalid input (message says what's wrong)
401
— missing or unknown x-api-key
404
— block/tx not found
429
— over 200 req/day; honour Retry-After (seconds to UTC midnight)
503
— node unreachable (8s timeout, retried once, fallback URL if set)

Headers: X-RateLimit-Limit / -Remaining / -Reset. Responses are cached for 30 seconds.

Developers · Fordnet