Skip to content

Aptos

Smart Router serves Aptos mainnet over the REST fullnode API. This page covers the supported methods, the example config, and how to connect a client.

Endpoint
Default port 3360 (override per endpoints[] entry)
Calling convention REST - GET /v1/..., POST /v1/view, etc.
chain-id APT1
Spec specs/aptos.json

Supported method families

Aptos exposes a REST API (not JSON-RPC). The native fullnode paths below are served under /v1. When you call them through the example config's listener, drop the /v1 from your request path, because the upstream URL already includes it. For example, for native GET /v1/accounts/{address}, call GET /accounts/{address} on the router. See the run section below.

Family Examples
Ledger / blocks GET /v1 (ledger info), GET /v1/blocks/by_height/{height}, GET /v1/blocks/by_version/{version}
Accounts GET /v1/accounts/{address}, GET /v1/accounts/{address}/resources, GET /v1/accounts/{address}/modules
Transactions GET /v1/transactions, GET /v1/transactions/by_hash/{hash}, POST /v1/transactions, POST /v1/transactions/simulate
View / state POST /v1/view, GET /v1/accounts/{address}/resource/{type}

The spec file linked above has the full method list.

Run this example

The repo has a ready-to-run config at config/smartrouter_examples/smartrouter_aptos.yml. It uses two public upstreams (PublicNode and the Aptos Labs fullnode) and needs no API key. REST has no websocket leg, so run it with --skip-websocket-verification:

SR_CONFIG=config/smartrouter_examples/smartrouter_aptos.yml \
  docker compose -f docker/docker-compose.yml up --build

smartrouter config/smartrouter_examples/smartrouter_aptos.yml \
  --use-static-spec specs/ --skip-websocket-verification

Then call it:

# ledger info (chain id, block height, ledger version)
curl http://127.0.0.1:3360/

The /v1 prefix lives in the node-url, not your request path

The example config's upstream URLs already end in /v1 (https://aptos-rest.publicnode.com/v1), and the router adds your request path to the end of that base. So call the listener at the root: GET /, GET /accounts/0x1, GET /blocks/by_height/{n}. Do not call GET /v1/.... That would resolve to /v1/v1/... upstream and return a 404 response.

Connect a client

# account resources - note the root-relative path (no /v1 prefix)
curl http://127.0.0.1:3360/accounts/0x1/resources

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

// The SDK appends /v1 itself, so point it at a node-url that does NOT
// bake in /v1 - drop the /v1 from the example config's upstreams and use
// the bare listener here.
const aptos = new Aptos(new AptosConfig({ fullnode: 'http://127.0.0.1:3360' }));
const info = await aptos.getLedgerInfo();

To use your own upstreams, edit the node-urls in the config. See The config file.