# ZooBC Gateway API Reference: Endpoints and Responses

> ZooBC Gateway API documentation: the proxy, status, allowlist, release, and CORS endpoints, with the request and response shapes a client needs to talk to the chain.

- Canonical page: https://zoobc.com/api-docs/
- Publisher: ZooBC, https://zoobc.com/
- Language: English. Translations: [中文（简体）](https://zoobc.com/zh/api-docs/), [Русский](https://zoobc.com/ru/api-docs/), [Italiano](https://zoobc.com/it/api-docs/), [Español](https://zoobc.com/es/api-docs/), [Français](https://zoobc.com/fr/api-docs/), [日本語](https://zoobc.com/ja/api-docs/), [한국어](https://zoobc.com/ko/api-docs/)
- Last updated: 2026-10-08
- Topics: API, Blockchain, Software documentation
- Keywords: ZooBC API, blockchain REST API, gateway API documentation, API reference, CORS, chain status endpoint, ZooBC gateway, developer documentation, ZooBC
- Site index for language models: https://zoobc.com/llms.txt

---

ZOOBC / API REFERENCE

## ZooBC Gateway API

ZooBC Gateway API documentation, including proxy, status, allowlist, release, and CORS endpoints.

### Choose a network

Each gateway documents the routes it really serves. The reference is generated from the running binary, not written alongside it.

TestNet zoobc.network

[Open the API reference](https://zoobc.network/api-docs)

MainNet zoobc.net

Open the API reference

MainNet opens 14 February 2027

01 / ONE BASE URL

### Everything under /api/v1

The whole chain API lives under `/api/v1` on any gateway, same origin as its reference page. No CORS to negotiate, no key to obtain, no rate plan.

`curl -s https://zoobc.network/api/v1/blockchain/status` returns the height, the confirmed height and the latest block. That is the shortest useful call and a good first check that a gateway is alive.

02 / READS AND WRITES

### They go to different places

A GET is proxied to an archival node, which holds the deep history: blocks, transactions and accounts as of any height. A POST is proxied straight to a full node, never to archival, because submitting a transaction needs a mempool.

That split matters more than it sounds. An archival node is a read-only history service and used to answer POST with a 404, which is why broadcasting through a gateway once did not work. The [developer guide](https://zoobc.com/developer) covers the routing and the allowlist in full.

03 / FOR PROGRAMS

### Reading it without a browser

A machine-readable guide to the same API is published by the gateway at [agents.md](https://zoobc.network/agents.md), with a discovery file at [llms.txt](https://zoobc.network/llms.txt) and a dependency-free Python reference at [zoobc-agent-example.py](https://zoobc.network/dl/zoobc-agent-example.py).

Those are served next to the chain deliberately: a guide that tells a program how to spend money should come from the same origin as the API it describes.