What is the Aptos API URL?

The Aptos Mainnet fullnode API URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/aptos/v1. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io, then use standard Aptos REST paths under it.

Is Aptos EVM compatible?

No. Aptos runs the Move VM, not the EVM. Contracts are written in Move, and clients use the fullnode REST API or the official SDKs instead of Ethereum JSON-RPC.

Does the official Aptos SDK work with BoltRPC?

Yes. Point the SDK's fullnode URL at your BoltRPC endpoint and everything else works unchanged.

What makes Aptos fast?

Block-STM, Aptos's parallel execution engine, processes independent transactions concurrently, and its consensus reaches finality in under a second.

What gas token does Aptos use?

APT, the native Aptos token, pays for gas. Fees are typically fractions of a cent.

Why do public Aptos fullnodes fail in production?

Public Aptos fullnodes apply strict per-IP rate limits that indexers and production apps hit quickly. A dedicated endpoint removes the per-IP ceiling.

Does BoltRPC support WebSocket for Aptos?

No, the Aptos fullnode API is REST over HTTPS and does not expose the WebSocket subscription model EVM chains use. Poll the REST routes for event-driven workloads.

Aptos API Endpoint

Aptos runs Move contracts with parallel execution and sub-second finality. Get a dedicated fullnode REST endpoint that keeps up with your indexer or app.

JSON-RPC 2.0

Start free trial Contact sales

LIVE LATENCY

53ms

LIVE

gateway round-trip · sampled every second

IN PRODUCTION AT Chainlink

Your endpoint, ready in one line.

Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.

HTTPS

https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/aptos

Replace YOUR_API_KEY with your API key. Get a free key →

Pick your stack.

Copy-paste examples for the libraries you already use. Swap the API key, hit run.

import { Aptos, AptosConfig, Network } from "@aptos-labs/ts-sdk";

const config = new AptosConfig({
  network: Network.MAINNET,
  fullnode: "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/aptos/v1",
});
const aptos = new Aptos(config);

const info = await aptos.getLedgerInfo();
console.log("Ledger version:", info.ledger_version);

const base = "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/aptos/v1";

const info = await fetch(base).then((r) => r.json());
console.log("Chain ID:", info.chain_id, "· version:", info.ledger_version);

curl https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/aptos/v1

Connect your dApp, bot, or indexer to Aptos Mainnet with BoltRPC. Aptos is the Move-language L1 with parallel transaction execution, and predictable request-unit pricing keeps your API costs flat while the chain processes transactions faster than most infrastructures can serve them.

Chain at a Glance


Protocol	Move-based Layer 1 (fullnode REST API)
Execution	Parallel (Block-STM)
Finality	Sub-second
Gas token	APT
Smart contracts	Move
EVM compatible	No (Move VM, REST API)

What Aptos is Built For

Aptos is a from-scratch Layer 1 built by the team behind Meta’s Diem project. Its differentiators are the Move language, a resource-oriented contract language designed for asset safety, and Block-STM, a parallel execution engine that processes independent transactions concurrently instead of single-file. The result is a chain built for consumer-scale throughput with sub-second finality, which has attracted DeFi, gaming and payments teams building for volume. Unlike EVM chains, Aptos exposes a REST API rather than JSON-RPC: clients fetch accounts, resources, blocks and transactions over HTTP paths, and the official TypeScript and Python SDKs wrap those routes. High-throughput chains punish slow infrastructure twice: more state to follow and less time before it changes. Exactly the case for a dedicated endpoint.

Common Use Cases on Aptos

Indexers and analytics pipelines Following a high-throughput ledger means sustained, continuous reads of blocks and transactions. A dedicated endpoint without per-IP limits is the difference between keeping up and falling behind.

DeFi backends Lending markets and DEXes on Aptos read Move resources (balances, positions, pool state) on short intervals, the same read-heavy pattern as EVM DeFi with REST semantics.

Payments and consumer apps Sub-second finality makes Aptos attractive for payment flows. Backends confirm transactions by polling GET /v1/transactions/by_hash; that latency is user-visible checkout time.

Gaming and high-volume mints Games and NFT platforms generate bursts of submissions and reads. Fixed request-unit pricing keeps burst days predictable on the invoice.

Built for teams that ship on Aptos.

Built for high-throughput reads

Parallel execution means Aptos state changes fast and in volume. Indexers and apps that follow the ledger poll continuously; a dedicated endpoint sustains that read rate without the throttling shared public fullnodes apply.

REST semantics, same billing model

Every Aptos route has a fixed, published request-unit weight, the same transparent pricing model as our JSON-RPC chains. One invoice logic across your whole multichain stack.

Sub-second finality needs fast confirmation reads

Payment and trading flows on Aptos confirm in under a second on-chain. Polling a slow API adds seconds back; BoltRPC's gateway round-trip is measured continuously against our own nodes.

Move ecosystem coverage from one provider

BoltRPC serves Aptos alongside Sui, the other major Move chain, plus Ethereum, Solana and 20+ other networks behind one dashboard and one key pattern.

Operator-grade reliability

Our node operator (Matrixed.Link, ISO/IEC 27001:2022 certified) tracks Aptos releases and network upgrades, so version bumps never become your incident.

Full JSON-RPC coverage.

Every standard Aptos method you would expect. Archive-only methods are available on request for qualifying plans.

STANDARD7

GET /v1GET /v1/accounts/{address}GET /v1/accounts/{address}/resourcesGET /v1/blocks/by_height/{height}GET /v1/transactions/by_hash/{hash}POST /v1/transactionsPOST /v1/view

Aptos, explained.

Common questions about connecting to Aptos over BoltRPC.

Ask a question →Read the docs

: The Aptos Mainnet fullnode API URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/aptos/v1. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io, then use standard Aptos REST paths under it.
: No. Aptos runs the Move VM, not the EVM. Contracts are written in Move, and clients use the fullnode REST API (or the official SDKs) instead of Ethereum JSON-RPC. MetaMask and ethers.js do not work with Aptos; use an Aptos wallet and the Aptos SDKs.
: Yes. Point the SDK's fullnode URL at your BoltRPC endpoint, new AptosConfig({ fullnode: "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/aptos/v1" }), and everything else works unchanged. The Python and other SDKs configure the same way.
: Block-STM, Aptos's parallel execution engine, processes independent transactions concurrently instead of one at a time, and its consensus reaches finality in under a second. The chain is designed for consumer-scale throughput.
: APT, the native Aptos token, pays for gas. Fees are typically fractions of a cent.
: Public Aptos fullnodes apply strict per-IP rate limits that indexers and production apps hit quickly: a high-throughput chain generates more state to read than most shared infrastructure will serve. A dedicated endpoint removes the per-IP ceiling.
: No, the Aptos fullnode API is REST over HTTPS and does not expose the WebSocket subscription model EVM chains use. Poll the REST routes or use the indexer pattern for event-driven workloads.

Ship on Aptos this week.

An API key in under 60 seconds, Aptos plus 34 other chains, and a team that answers when you write.

Start free trial View pricing