Mainnet
Mainnet REST API
https://vechain-mainnet.gateway.tatum.io
Free VeChain RPC (VET)
Discover VeChain, a blockchain optimized for enterprise solutions and supply chain management. Build decentralized applications using its RPC gateway.
99.9%
2
24/7
FREE
Gateway
Connect to VeChain
Access reliable, enterprise-grade endpoints that power your dApp with ultra-low latency and 99.9% uptime.
Connect to VeChain Gateway
Make your first RPC call on VeChain's Blockchain Gateway.
Testnet
Testnet REST API
https://vechain-testnet.gateway.tatum.io
* Rate limit enabled - perfect for testing and development. For production, we recommend to Upgrade.
Ready for production?
Get 200 requests/second, priority support and advanced blockchain features.
Global Load Balancer
Route to nearest node
Batch RPC Calls
Multiple requests at once
Archive Nodes
Historical blockchain data
Debug & Trace
Advanced debugging
Advanced Analytics
Usage & performance
Bring Your Own RPC
Custom RPC gateways
Get Free API Key
Increase your limit and access all network features in Tatum Development Platform.
Estimate Gas on VeChain
Calculate the optimal gas fee for any transaction on VeChain.
Smart Contract Tools on VeChain
Deploy, create, and interact with smart contracts on VeChain.
Accessible to Everyone
No signup. No paywalls. Just RPC that works. Great ideas come from everywhere.
Our Mission
With love by Tatum
Method reference
VeChain methods
Every method the VeChain gateway accepts, grouped by interface. 21 in total, read live from the node rather than kept by hand.
Mainnet is the live VeChain network. Every transaction it
accepts is final, and every VET balance it
reports is real money.
Testnet answers the same methods on a network funded with tokens that have no market value. Develop there, then change the URL to Mainnet when the code is stable. Nothing else about your integration has to change.
Everything below is served over REST. Its endpoint differs per network, and all of them are in the gateway list above.
What sits between you and VeChain
A node is a machine running VeChain with a copy of the chain. Your code cannot ask the chain directly, it asks a node. The gateway picks a healthy one for every call, so you point at one URL instead of one machine.
Your application
FREE RPC gateway picks a healthy node
Node Node Node
- One URL, nothing to run or keep patched yourself.
- Calls routed to a node that is up and in sync.
- A failing node is skipped rather than returned to you as an error.
REST
21 methods https://vechain-mainnet.gateway.tatum.io
Every resource has its own URL, so a request is just an address you can open.
Paste it into a browser, curl it, or bookmark it. There is no body to construct and no method name to look up, and because a read is a plain GET, ordinary HTTP caching applies at the CDN and in your own client. Responses are JSON, and the path itself usually tells you what you are getting.
Where it fits
- Getting oriented on an unfamiliar chain without writing any code first.
- Caching, because a GET can be cached by anything sitting between you and the node.
- Debugging, since the request that failed is a URL you can paste to a colleague.
Trade-offs
- You get exactly what the endpoint returns. There is no way to ask for less, or for more.
- Building a full picture takes several round trips where one batched JSON-RPC call would do.
- Paths carry version prefixes and shift between node releases more readily than method names do.
Enabled and tested methods
Read live from the endpoint, so this is what it actually serves today rather than what the protocol allows in principle. Anything not on this list returns a method-not-found error.
- GET /accounts/{address}
- Fetches an account, including balance, nonce and contract details.
- GET /accounts/{address}/code
- Returns the contract bytecode deployed at an address.
- GET /accounts/{address}/storage/{key}
- Reads a single storage slot from a contract.
- GET /blocks/{revision}
- Returns a block by number, ID, or the keyword best.
- GET /fees/history
- Returns base fee and gas usage across recent blocks.
- GET /fees/priority
- Returns a suggested priority fee.
- GET /node/network/peers
- Lists the peers the node is connected to.
- GET /node/txpool
- Lists the transactions waiting in the pool.
- GET /node/txpool/status
- Returns how many transactions are waiting in the pool.
- GET /transactions/{id}
- Returns a transaction by its ID.
- GET /transactions/{id}/receipt
- Returns the receipt of a transaction, including gas used and events.
- POST /accounts/{address}
- Calls a contract read-only at a given address.
- POST /accounts/*
- Runs a batch of read-only contract calls in one request.
- POST /debug/storage-range
- Walks a range of contract storage from a starting key.
- POST /debug/tracers
- Traces the execution of a clause in an existing transaction.
- POST /debug/tracers/call
- Traces a call without submitting it.
- POST /events
- Queries contract event logs by address, topic and block range.
- POST /logs/event
- Queries contract event logs with filtering and paging.
- POST /logs/transfer
- Queries native VET transfer logs.
- POST /transactions
- Submits one or more signed transactions.
- POST /transfers
- Queries native token transfers by address and block range.
Common REST errors
What you are most likely to hit calling this interface, and what to do about it.
- 400
- Bad request. A path or query parameter is malformed. Check the parameter format, and that path values are URL-encoded.
- 404
- Not found. Either the path is wrong, or the resource genuinely does not exist at that height. Confirm the path against the list above. A valid path can still 404 for pruned history on a non-archive node.
- 429
- Rate limited. You have exceeded the free tier request allowance. Back off and retry. REST responses cache well, so caching on your side removes most repeat traffic.
- 500
- Internal server error. The node failed while handling the request. Retry with backoff.
- 503
- Service unavailable. The node is starting, resyncing, or temporarily out of rotation. Retry with backoff; this is normally short-lived.
Blockchain Data
Indexed VeChain Data Insights
Complete on-chain data access, no infrastructure to run yourself. Query wallets, tokens, NFTs, and transaction history with lightning-fast APIs.
Learn more
About VeChain
What it is, and guides for building on it.
The VeChain RPC documentation provides developers with the necessary tools to interact with the VeChain blockchain programmatically. VeChain is designed for enterprise use cases, particularly in supply chain management, using a proof-of-authority (PoA) consensus mechanism for efficient, low-cost transactions. The documentation includes API endpoints for querying blockchain data, managing transactions, and deploying smart contracts. Developers can leverage VeChain’s robust architecture to build decentralized applications (dApps) integrated with enterprise supply chains, improving transparency and efficiency.
What's new at Tatum on VeChain?
Oct 8, 2026 Added
Notifications: Robinhood
Robinhood Chain is now live on Tatum’s Blockchain Notifications, with support for all notification types. Receive onc...
Oct 7, 2026 Added
RPC Gateway: WebSockets for Arbitrum and BSC
Stop polling. Start streaming. Tatum WebSocket subscriptions push blockchain updates to your app over a persistent co...
Sep 25, 2026 Deprecated
Harmony Networks Removal
Tatum is decommissioning its hosted Harmony Mainnet S0, Harmony Testnet S0, and Harmony Devnet S0 RPC services follow...
FAQ
Frequently Asked Questions
Everything you need to know about VeChain RPC endpoints
Quick Answer: What is VeChain RPC?
RPC (Remote Procedure Call) is the standard way to interact with the network programmatically - reading on-chain data, submitting transactions, and deploying smart contracts through JSON-RPC calls. The free tier ships 5 requests per minute with no registration required, which covers most learning and testing workflows. Production applications typically move to Tatum Premium for 200 requests per second and enterprise-grade reliability.
What is VeChain RPC?
RPC (Remote Procedure Call) is the interface that lets developers interact with the network: read on-chain data, submit transactions, and deploy smart contracts programmatically over standard JSON-RPC methods, without running your own node.
How do I connect to VeChain using these RPC endpoints?
Simply copy the RPC endpoint URL from above and configure it in your Web3 library (ethers.js, web3.js), wallet (MetaMask, Trust Wallet), or development tool (Hardhat, Truffle). The endpoint works immediately with no registration required for the free tier.
What are the rate limits for the free RPC tier?
Free tier RPC endpoints are limited to 5 requests per minute. This is perfect for testing and development. For production applications, we recommend upgrading to Tatum Premium which offers 200 requests per second with no daily limits.
Is VeChain RPC free forever?
Yes! Our free tier RPC endpoints are free forever with 5 requests per minute. This tier is perfect for learning, testing, and small projects. There are no hidden fees or time limits on the free tier.
What happens if I exceed the free tier rate limit?
If you exceed 5 requests per minute on the free tier, you'll receive an HTTP 429 (Too Many Requests) error. This is a standard rate limiting response. To avoid this, you can upgrade to Tatum Premium which offers 200 requests per second with no daily limits, perfect for production applications.
Can I use these VeChain RPC endpoints with MetaMask?
Yes! You can configure MetaMask to use our RPC endpoints. Simply copy the endpoint URL from above, go to MetaMask Settings > Networks > Add Network (or edit existing), and paste the RPC URL. This works with all EVM-compatible networks, including this one.
Are these RPC endpoints secure?
Yes, all our RPC endpoints use HTTPS encryption and follow enterprise-grade security practices. They're powered by Tatum's infrastructure which maintains 99.9% uptime.
What's the difference between mainnet and testnet RPC endpoints?
Mainnet carries real transactions with real value, so every write is final. Testnet runs on a separate network funded with free test tokens, which makes it the safe place to try new code, retry failed calls, and simulate edge cases. Always validate on testnet before pointing production traffic at mainnet.
How do I troubleshoot RPC connection errors?
If you're experiencing connection errors, check: 1) The RPC endpoint URL is correct, 2) You're not exceeding rate limits (5 req/min for free tier), 3) Your network allows HTTPS connections, 4) The network is currently operational. For persistent issues, check our status page or contact support.
Can I use these endpoints in production?
Free tier endpoints can be used in production for low-traffic applications (under 5 req/min). For production apps with higher traffic, we strongly recommend Tatum Premium for guaranteed uptime, faster rate limits, and enterprise SLA.
Related Blockchains
Explore Other Blockchains
Discover RPC endpoints for other popular blockchain networks
