TronGrid V1 API is a set of high-performance extension APIs provided by TronGrid on top of standard TRON node HTTP APIs, covering accounts, transactions, contracts, events, blocks, TRC-10 assets, and AI Agent query capabilities.
TronGrid V1 API is a set of extension APIs provided by TronGrid on top of standard TRON node HTTP APIs. It is designed for high-frequency queries and business integrations. TronGrid pre-indexes on-chain data and exposes common queries such as account history, Token transfers, contract events, internal transactions, and block statistics through ready-to-use HTTP endpoints.
If you only need to build, sign, or broadcast transactions, use FullNode HTTP API. If you need to query solidified state, use Solidity HTTP API. If you need account history, event logs, TRC-20 transfers, contract interaction history, or aggregate statistics, TronGrid V1 API is usually more suitable than scanning blocks directly.
TronGrid V1 API covers Mainnet, Shasta Testnet, and Nile Testnet. Production requests need an API key and should use quota and rate-limit settings that match your traffic profile. For the overall TronGrid node service and extension API description, see TronGrid.
V1 API categories
| Category | Entry | Main purpose |
|---|---|---|
| API key and network configuration | API Key | Create and manage API keys, view network endpoints, security settings, and rate-limit policies |
| Accounts and transactions | Accounts and transactions | Query account information, account transaction history, TRC-20 transfers, internal transactions, and Token balances |
| TRC-10 assets | Assets (TRC-10) | Query TRC-10 assets by ID, name, or issuer, or list on-chain TRC-10 assets |
| Contracts | Contracts | Query contract transaction history, contract internal transactions, TRC-20 Token information, and holder balances |
| Events | Events | Query smart-contract event logs by transaction, contract, block, or latest block |
| Blocks | Blocks | Query pre-indexed block aggregate statistics from TronGrid |
| MCP API | MCP API | Expose TRON query capabilities to AI clients and custom Agents through Model Context Protocol |
| TRON AI Agent skills | TRON AI Agent skills | Use prebuilt skills to query TRON on-chain data through natural language |
Common use cases
Query account history
Use the accounts and transactions APIs to query an address's transaction history, TRC-20 transfers, internal transactions, or Token balances. Compared with parsing blocks transaction by transaction, V1 API is already indexed by address and is more suitable for account history, asset flows, and dashboards.
Query contract events
Use the events APIs to query Event Logs by transaction ID, contract address, block number, or latest block. This is useful for listening to TRC-20 / TRC-721 transfers, contract business events, and DApp backend state synchronization.
Query contract and Token data
Use the contracts APIs to query contract transaction history, internal transactions, TRC-20 Token information, and holder balances. Use the TRC-10 assets APIs to query on-chain TRC-10 asset lists and asset details.
Connect AI Agents
Use MCP API or TRON AI Agent skills to connect TronGrid on-chain queries to Claude, Cursor, or custom Agents. These features are suitable for natural-language account profiling, transaction analysis, Token queries, block queries, and data insights.
Network endpoints
| Network | Base URL |
|---|---|
| Mainnet | https://api.trongrid.io |
| Shasta Testnet | https://api.shasta.trongrid.io |
| Nile Testnet | https://nile.trongrid.io |
API key
Production requests should include an API key for quota management and rate-limit control. Requests without an API key may be severely rate-limited or rejected. For creating, configuring, and protecting API keys, see API Key. For rate limits and backoff strategy, see Rate limits.
Client-side security note
TRON APIs reduce XSS risk by setting the HTTP API Content-Type to application/json, but clients should still treat all API responses as external input. Escape API response data before rendering it in a UI. This also applies to responses that use Base58Check addresses when visible = true.
Related resources
- TronGrid — TronGrid node service and extension API introduction
- RPC and indexer providers — choosing hosted RPC, indexers, or self-hosted nodes
- API Key — network endpoints, API key creation, and request header format
- Rate limits — request quota, 429 / 403 responses, and backoff strategy
- FullNode HTTP API — standard TRON node HTTP read/write interface
- Solidity HTTP API — read-only interface based on solidified blocks