IoTex RPC Endpoints & API Access

IoTex RPC Endpoints

IoTex is a purpose-built Layer 1 blockchain designed to connect smart devices to smart contracts, powering the DePIN (Decentralized Physical Infrastructure Networks) ecosystem. As an EVM-compatible chain, IoTex enables developers to build and deploy decentralized applications that interact with real-world IoT devices and data.

What Developers Use IoTex RPC For

IoTex RPC endpoints allow applications to read blockchain data, submit transactions, and interact with smart contracts on the IoTex network. Common use cases include:

• DePIN dApps: Manage device registries, verify off-chain data, and coordinate physical infrastructure.
• Wallets: Check balances, send IOTX tokens, and interact with DeFi protocols.
• Analytics & Indexing: Query historical data for dashboards, explorers, and data pipelines.
• Backend Services: Automate contract interactions, monitor events, and power bots.

IoTex RPC on OnFinality

OnFinality provides managed IoTex RPC API endpoints with the following capabilities:

• Protocol: EVM JSON-RPC (compatible with Ethereum tooling)
• Transport: HTTP and WebSocket
• Advanced Access: Archive node support for historical data queries
• Network: Mainnet (Chain ID: 4689)

Developers can use OnFinality's IoTex RPC endpoints for production workloads without running their own node infrastructure. The service includes request analytics, usage visibility, and a clear scaling path from shared APIs to higher-capacity plans.

Key Considerations for IoTex RPC

When choosing an IoTex RPC provider, consider:

• Archive vs Full Node: Archive nodes store the complete historical state, essential for applications that need past data (e.g., analytics, compliance). OnFinality supports archive access for IoTex.
• Rate Limits: Public endpoints may have restrictive rate limits. Authenticated endpoints provide clearer limits and higher throughput.
• Latency & Reliability: OnFinality's infrastructure is designed for consistent performance, though actual latency depends on geographic region and network conditions.

Getting Started with IoTex RPC on OnFinality

1. Create or sign in to your OnFinality account.
2. Select IoTex from the supported networks list.
3. Create an API endpoint (shared or dedicated, if supported).
4. Test the endpoint using eth_blockNumber or your preferred method.
5. Monitor usage, errors, and limits before moving critical traffic.

For detailed setup instructions, refer to the OnFinality documentation.

IoTex RPC and developer resources

A useful IoTex RPC page should make the connection path, supported capabilities, and production planning trade-offs clear before a developer opens the dashboard.

Best fit: mainnet production workflows for wallet flows, contract apps, and live backends.

What builders usually check first:

• Read current chain state for apps, dashboards, wallets, and backend services.
• Submit transactions and monitor confirmations from Ethereum-compatible tools.
• Query logs, receipts, and historical state when indexers or analytics pipelines need more than the latest block.
• Debug contract behaviour with trace data where the network supports it.

Supported capability notes:

• Authenticated IoTex RPC/API access for wallet flows, contract apps, and live backends.
• Flexible HTTP and WebSocket access for app, backend, and integration workflows.
• Archive-capable workflows when the product needs older chain state.

Decision notes:

• Environment: mainnet. Protocol family: EVM JSON-RPC.
• Flexible HTTP and WebSocket access is listed for supported app and backend workflows.
• Archive support is available for historical state or older chain-data queries.

A quick connection check usually starts with eth_blockNumber, then moves into the exact methods your wallet, dashboard, bot, indexer, or backend service needs.

Planning the next step:

• Shared RPC is a practical starting point for integration, prototypes, dashboards, and many app backends.
• If your product becomes traffic-heavy or operationally sensitive, review the available upgrade path before relying on a single access pattern.

Next steps:

• Create or manage RPC endpoints
• Review RPC pricing
• Read the RPC provider selection guide