An address state + delegation
API · /tezos-api
Tezos (XTZ) On-Chain API
Live on-chain data from the Tezos blockchain (XTZ), a self-amending liquid-proof-of-stake Layer 1, served from the public TzKT indexer API — no key, nothing cached. The account endpoint returns any address's state: its XTZ balance, account type, the baker it delegates to, its staked balance, transaction count and first-activity date. The tokens endpoint returns the FA1.2 and FA2 token balances an address holds, with the token contract, symbol and decoded amount. The operations endpoint returns the account's most recent transactions with the counterparty, amount, status and time. The network endpoint returns the live chain state: the head block level, the current cycle, the active protocol and the total XTZ supply. Everything is read live from TzKT, nothing stored. This is the Tezos on-chain layer for any wallet, explorer, baking, NFT or analytics app. Distinct from the XRP Ledger, Stellar, TRON, Aptos, Algorand, EVM and Solana on-chain APIs and from price feeds — this is Tezos account state, delegation, token balances, operations and ledger health. 4 endpoints, no key on our side.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 122 ms
- Server probes · 24h
- Subscribers
- 3,747
- active
- Total calls
- 95
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 3,800 calls / month
- 5 requests / second
- Hard cap (429 above quota, no overage)
- 3,800 calls/month
- 5 req/sec
- Account, network, delegation
- No credit card
Starter
€13.00 /month
- 98,000 calls / month
- 12 requests / second
- Hard cap (429 above quota, no overage)
- 98,000 calls/month
- 12 req/sec
- Token balances + operations
- Email support
Pro
€30.00 /month
- 590,000 calls / month
- 30 requests / second
- Hard cap (429 above quota, no overage)
- 590,000 calls/month
- 30 req/sec
- Wallet, baking & NFT pipelines
- Priority support
Mega
€71.00 /month
- 3,100,000 calls / month
- 80 requests / second
- Hard cap (429 above quota, no overage)
- 3,100,000 calls/month
- 80 req/sec
- Exchange & analytics scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Tezos Bigmaps API
Read Tezos's on-chain key-value storage (bigmaps) live from the public TzKT indexer — no key. A bigmap is Tezos's lazily-deserialised on-chain map: the data structure smart contracts use for the big stuff — token ledgers (who owns what), NFT ownership, allowances and metadata. The Tezos contract explorer lists contracts and their interface, but it cannot browse the bigmaps themselves, read a bigmap's typed key/value schema, or page through its live key-value entries. This opens that. Browse and rank the bigmaps by size with their pointer, owning contract, path (e.g. "ledger"), tags and total/active key counts; read one bigmap's detail and its typed key/value schema (what shape each row's key and value take, e.g. an address-to-nat token ledger); and page through a bigmap's live key-value entries — the actual on-chain data, such as the address-to-balance rows of a token ledger or the owner rows of an NFT collection. The storage / data layer for Tezos explorers, indexers, token dashboards and analytics. Distinct from the Tezos on-chain reader (account state), the smart-contract explorer, the FA-token registry and the .tez naming reader. Live from the indexer; short cache only.
api.oanor.com/tezosbigmaps-api
Tezos Smart Contract API
Browse Tezos smart contracts live from the public TzKT indexer — no key. On Tezos a smart contract is an originated KT1 account with Michelson code, on-chain storage and named entrypoints. The Tezos on-chain reader resolves a single address's account state, but it cannot browse the contract universe, rank contracts by balance or activity, read a contract's callable entrypoints, or read its code identity. This opens that. Browse and rank the deployed smart contracts with their KT1 address, XTZ balance, creator, lifetime transaction count and token activity; read one contract in full — its balance, creator, code/type hash (contracts sharing a code hash run identical Michelson) and current delegate; and read the named entrypoints a contract exposes — its callable interface, each method with its parameter schema. The contract layer for Tezos explorers, dApp dashboards, wallets and analytics. Distinct from the Tezos on-chain reader (per-address account state), the self-amending governance reader, the baker reader, the FA-token registry and the .tez naming reader. Live from the indexer; short cache only.
api.oanor.com/tezoscontracts-api
Tezos Domains (.tez) API
Read the Tezos Domains naming service live from the public TzKT indexer — no key. Tezos Domains maps human-readable .tez names to Tezos addresses, the way ENS maps .eth names on Ethereum. None of the Tezos on-chain, governance, baker, smart-rollup or FA-token readers expose the naming layer; this opens it. Browse the most recently active .tez domains with their owner address, the address they point to, registration level and expiry; forward-resolve a .tez name to the address that owns it (how a wallet turns "alice.tez" into a tz1 address); and reverse-resolve any Tezos address to the .tez names registered to it (an address can own several). The identity / naming layer for Tezos wallets, explorers, payment UX and analytics. Distinct from the Tezos on-chain reader, the self-amending governance reader, the baker reader, the smart-rollup reader and the FA-token registry. Live from the indexer; short cache only.
api.oanor.com/tezosdomains-api
Tezos FA Token & NFT API
Browse the Tezos token universe live from the public TzKT indexer — no key. Tezos tokens are FA1.2 (fungible) and FA2 (fungible or NFT) contracts. The Tezos on-chain reader returns the token balances a single address holds, but it cannot browse the token universe, rank tokens by holders, list who holds a token, or trace a token's transfers. This opens that. Discover and rank FA tokens and NFT collections with their TzKT token id, contract, standard, name, symbol, decimals, holder and transfer counts, decimal-adjusted total supply and — for NFTs — their resolved artwork image; list the holders of any token with their decoded balances, largest first; and trace a token's recent transfers with sender, receiver, decimal-adjusted amount and time (a mint shows no sender, a burn no receiver). The discovery, NFT and distribution layer for Tezos wallets, token explorers, NFT marketplaces and analytics. Distinct from the Tezos on-chain reader (per-address token balances), the self-amending governance reader, the baker/validator reader and the smart-rollup reader. Live from the indexer; short cache only.
api.oanor.com/tezostokens-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Tezos (XTZ) On-Chain API?
What's the rate limit for Tezos (XTZ) On-Chain API?
How much does Tezos (XTZ) On-Chain API cost?
Can I cancel my subscription anytime?
Is Tezos (XTZ) On-Chain API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/tezos-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/tezos-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/tezos-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/tezos-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.