Migration guide

Moving a Blockberry Mina API client to mina-explorer-api.

The one change: swap the base URL, keep everything else.

- https://api.blockberry.one/mina-mainnet/v1/...
+ https://mina-explorer-api.minaprotocol.com/mina-mainnet/v1/...

What stays the same

The x-api-key request header — same header name, same placement.
The /mina-{network}/v1/... path structure — every path, query param, and method is unchanged.
Response shapes, envelopes, content-types, and even bug-compatible quirks (e.g. blockHeight as a string on transaction lists).

What changes

Your API key value is not portable. Blockberry keys are not shared with us; you must request a new key — see Get an API key. The header is identical; only the value is re-issued by us.
Intentional divergences — a set of fields are always null (off-chain metadata with no public on-chain source) and a few groups are stubs. These are enumerated, per endpoint and per field, in the compatibility matrix rather than restated here.

Verify the switch

After changing the base URL, a quick smoke check:

curl -H "x-api-key: $YOUR_KEY" \
  https://mina-explorer-api.minaprotocol.com/mina-mainnet/v1/blocks/latest-block-state-hash

Interactive reference: Swagger UI · ReDoc · OpenAPI spec.

← Back to the compatibility matrix

mina-explorer-api — a drop-in, bug-compatible replacement for the Blockberry Mina REST API. Compatibility data is generated from docs/compatibility.yaml, the same source of truth the gate_m4_t3 test suite asserts against.