Tezos API

Tezos is an community-governed, open-source blockchain network capable of running complex smart contracts for asset settlement and decentralized applications (dApps).

Networks Mainnet, Testnet
Released 2018
Consensus Liquid proof of stake (LPoS)
Smart contracts Yes
Block time 30 seconds
Smart contract language(s) supported Michelson, LIGO, SmartPy, Morley, Fi, and Archetype
Get started with Tezos

The Tezos API — build without running a node

Access Tezos blockchain data through one unified REST API: transaction and address data, balances, block data, and real-time webhooks for on-chain events — with no Tezos node to run and maintain. Start free and scale as you grow.

Blockchain data

Read Tezos transactions, addresses, balances, UTXOs, and block data through one REST API.

Real-time webhooks

Subscribe to on-chain events — incoming and outgoing transactions, confirmations, and mined blocks.

No node to run

Skip the infrastructure — managed, always-synced access with no node to operate or maintain.

Building a full wallet? Explore HD Wallets.

Need prices too? See the crypto price API, or run your own Tezos RPC nodes.

The self-amending blockchain

Tezos is a self-amending crypto ledger which means it can upgrade itself based on user voting without having to split (“fork”) the network into two different blockchains. Tez (XTZ) is the native token of the Tezos blockchain.

Frequently Asked Questions

Which blockchain does Tezos run on?

Tezos settles on Tezos. A first transfer from an unrevealed account needs its public key revealing, which is why fee estimation asks for it — a step that has no equivalent on an EVM chain.

What kind of chain is Tezos?

It is an account-model chain with FA1.2 and FA2 token standards.

Can I test Tezos without spending real funds?

Yes — the same endpoints serve Tezos's Ghostnet testnet, so you can build and verify an integration end to end before you touch mainnet.

How do I read Tezos balances and transfers?

Use Address Latest for current state and recent activity — it needs no setup and answers for roughly the last 14 days. For a full history, Address History requires the address to be synced first, which then bills per address per day for as long as it stays synced.

What does reading Tezos data cost?

It depends on the endpoint family rather than on Tezos itself: single-record calls are charged per request, while list endpoints are charged per page returned, and a synced address adds a daily monitoring charge. The pricing calculator has the current per-chain figures.