Make your first authenticated Tatum API call with your own API key, then find the reference for the API you need.
1Pick a language
2Credentials
3Try It!
Loading…
Try It! to start a request and see the response here! Or choose an example:Log in to docs.tatum.io with your Tatum Dashboard account to make the call above with your own API key. No account yet? Create one for free.
The call above, GET /v3/tatum/version, confirms that your key works. The response shows the plan of the key, whether it is a testnet key, the plan's credit limit, and the credits used. Header formats, key management, and errors: Authentication.
Before you build
- Pick the right key. Every account has a mainnet key and a testnet key. Start on testnet, and get test funds from the Testnet Faucets.
- Check your limits. Every request costs credits, and each plan has a requests-per-second limit. See Plans & Limits.
- Protect your key. Keep it server-side, and add access restrictions to keys used in browsers or apps.
Base URLs
| API | Base URL |
|---|---|
| Blockchain Data, Notifications, and REST API | https://api.tatum.io |
| RPC Gateway | https://{chain}-{network}.gateway.tatum.io, for example https://ethereum-mainnet.gateway.tatum.io |
Chains, networks, and their RPC URLs: Supported Blockchains.
Monitor and debug
- My Requests: requests you made with your keys, with status codes and response bodies.
- Access Logs in the Tatum Dashboard: request history for your keys.
- Errors: RPC Gateway error codes, HTTP 429, Authentication errors.
- Platform status: status.tatum.io.
Connect your AI tools
Add the Tatum Documentation MCP server to Cursor, Claude Code, VS Code, or another MCP client so your assistant can search these docs, look up endpoints, and call the API with your key:
https://docs.tatum.io/mcpSetup per client: Documentation MCP.
Get help
Reporting HTTP errors lists what to include in a ticket. Then reach us through Contacting Support, or ask the community on Discord.