Logo
Aptos logo

Aptos RPC Endpoint and API

Aptos uses its own API surface rather than EVM JSON-RPC, so production checks should cover account, transaction, block, and ledger endpoints your app depends on.

Sign up for a Free Plan to unlock up to 40 req/sec and API Usage and Performance Insights. Get Started

Public endpoint rate limit: 5 req/sec

Quick Start
curl 'https://aptos.api.onfinality.io/v1/public'
curl 'https://aptos.api.onfinality.io/v1/public'
HTTPs
https://aptos.api.onfinality.io/v1/public
https://aptos.api.onfinality.io/v1/public

Go to Growth Plan

  • High Performance
  • Powerful RPC Analytics
  • Up to 500 rps
  • No daily response limit
  • Priority Support
  • Decentralized Servers
Get Started

Aptos endpoint details

  • Common methods to test: GET /v1, GET /v1/accounts/{address}, GET /v1/transactions/by_hash/{hash}, GET /v1/blocks/by_height/{height}
  • Best-fit workloads: Move application backends, wallet account reads, DeFi integrations, ledger and transaction lookups

OnFinality Aptos RPC features

  • Common Use Cases: dApps, wallets, DeFi, analytics, games, bots, backend services

Build faster with Aptos RPC endpoints

Use OnFinality's Aptos RPC APIs to connect wallets, dApps, dashboards, bots, and backend services without operating your own node from day one.

Public endpoint testing

Start with the Aptos public RPC endpoint for lightweight checks, prototypes, and quick integration tests.

Authenticated API access

Move production traffic to authenticated endpoints when you need clearer limits, analytics, and operational visibility.

Standard RPC methods

Query Aptos blocks, transactions, balances, events, and chain state through HTTP and WebSocket workflows.

Operate Aptos infrastructure with more control

Production teams need more than an endpoint URL. They need observability, predictable capacity, and a path from shared RPC access to isolated infrastructure.

Request visibility

Track usage patterns and response activity so your team can understand traffic growth before it becomes an incident.

Dedicated node path

Use dedicated Aptos nodes when your workload needs isolated resources, custom operations, or stronger capacity planning.

Archive and historical data

Plan for archive access when analytics, audits, indexers, or advanced app features need older Aptos state.

Choose the right Aptos RPC setup

Different Aptos products need different infrastructure. OnFinality gives teams a practical path from public RPC testing to production-grade API and node operations.

For prototypes

Use public RPC for simple reads, connection checks, and early experiments where strict performance guarantees are not required.

For live apps

Use authenticated API endpoints when users depend on stable request handling, monitoring, and scalable access.

For heavy workloads

Use dedicated nodes for sustained traffic, latency-sensitive services, validator tooling, exchange systems, and indexing pipelines.

Never Worry about Infrastructure Again

OnFinality takes away the heavy lifting of DevOps so you can build smarter and faster.

Get Started