Public Worker Base URL · https://api.n3index.dev

Verified live APIs for Neo N3 builders

N3Index exposes a single Cloudflare-worker API surface at https://api.n3index.dev. Use curated /indexer/v1 endpoints for product integrations, and the live /rest/v1 schema for PostgREST access to explorer data, contract intelligence, metadata caches, and analytics views.

Explore Quick Start Open REST Schema OpenAPI JSON

api.n3index.dev

One public base URL for health, curated indexer endpoints, and the live REST schema behind the worker.

Mainnet + Testnet

Status endpoints for both networks are live, cache-backed, and available through the same public edge.

Contract Intelligence

Events, executions, signers, notifications, NEP-17 transfers, and NEP-11 transfers are all queryable today.

Live REST Schema

/api renders the worker’s public /rest/v1 schema in real time.

Live Network Dashboard

Real-time mainnet and testnet telemetry from the public worker at https://api.n3index.dev. Chain totals come from the live summary endpoint, while indexed coverage shows how much history is already materialized inside N3Index. The dashboard refreshes automatically every 15 seconds and can be refreshed manually at any time.

Connecting to live network data...
Mainnet

Neo N3 Mainnet

Production network health, explorer totals, indexed progress, and the newest blocks.

Loading
Indexed Block
—
Last block currently indexed
Chain Tip
—
Current network tip observed
Lag Blocks
—
How far behind the tip the indexer is
Total Transactions
—
Explorer-style total served through the N3Index summary endpoint
Total blocks: — Total assets: — Total addresses: — Active 7d: — Indexed tx: — Indexed coverage: — Latest block: — Latest block time: — Last refresh: —
Block Transactions Produced Hash
Loading recent blocks…
Testnet

Neo N3 Testnet

Developer-network telemetry with explorer totals, indexed progress, and the newest blocks.

Loading
Indexed Block
—
Last block currently indexed
Chain Tip
—
Current network tip observed
Lag Blocks
—
How far behind the tip the indexer is
Total Transactions
—
Explorer-style total served through the N3Index summary endpoint
Total blocks: — Total assets: — Total addresses: — Active 7d: — Latest block: — Latest block time: — Last refresh: —
Block Transactions Produced Hash
Loading recent blocks…

Two ways to build

N3Index provides two integration modes tailored to different development needs: a polished product API for frontend applications, and a raw query layer for advanced data consumers.

Application API

The Indexer API is the recommended entry point. It returns stable, structured JSON views over indexed blockchain activity.

Best for Wallets & Explorers

Raw Data Access

The REST API offers direct PostgREST access. Use SQL-like syntax in your URLs: select, eq., in., limit, and offset.

Best for Analytics & Data Science

Decoded Events

We handle the complex ABI decoding. Query clean, readable on-chain events without manually parsing raw application logs.

Best for Smart Contract DApps

Quick Start

These live examples hit the public worker directly at https://api.n3index.dev.

Mainnet Status 
curl --location   'https://api.n3index.dev/indexer/v1/networks/mainnet/status'
Testnet Summary 
curl --location   'https://api.n3index.dev/indexer/v1/networks/testnet/summary'
Hot Contract Events 
curl --location   'https://api.n3index.dev/indexer/v1/networks/mainnet/contracts/0x48c40d4666f93408be1bef038b6722404d9a4c2a/events?event_name=Transfer&limit=5'
Token Overview 
curl --location   'https://api.n3index.dev/indexer/v1/networks/mainnet/tokens/0x00fb9575f220727f71a1537f75e83af9387628ff'
REST Contract Events 
curl --location   'https://api.n3index.dev/rest/v1/contract_events?network=eq.mainnet&contract_hash=eq.0x48c40d4666f93408be1bef038b6722404d9a4c2a&event_name=eq.Transfer&limit=5'
REST Execution Feed 
curl --location   'https://api.n3index.dev/rest/v1/transaction_executions?network=eq.mainnet&limit=1'

Public API Reference

The home page summarizes the curated product API and the most important REST datasets. The full live /rest/v1 schema is always available on /api.

Indexer API Reference

These endpoints are hand-designed JSON resources for wallets, dashboards, monitoring, bots, and DApp backends.

Method Endpoint Description
GET /indexer/healthz Worker-exposed health check for the curated indexer service.
GET /indexer/v1/networks/{network}/status Mainnet or testnet indexing status, freshness, and lag metrics.
GET /indexer/v1/networks/{network}/summary Explorer-style network totals plus indexed progress in one response for dashboard and monitoring surfaces.
GET /indexer/v1/networks/{network}/accounts/{address} Account summary including sent/signed activity and NEP transfer totals.
GET /indexer/v1/networks/{network}/accounts/{address}/transactions Recent transactions for an account, including signer participation.
GET /indexer/v1/networks/{network}/contracts/{contractHash} Contract overview. Very hot contracts may return -1 for expensive aggregates instead of timing out.
GET /indexer/v1/networks/{network}/contracts/{contractHash}/events Paginated decoded contract events with filters for event name, tx hash, and block height.
GET /indexer/v1/networks/{network}/tokens/{contractHash} Token activity overview including transfer counts and holder information.
GET /indexer/v1/networks/{network}/analytics/daily Daily chain analytics such as tx counts, fee burned, and transfer activity.
GET /indexer/v1/networks/{network}/metadata/validators Validator directory with logos, votes, active state, and rank.
GET /indexer/v1/networks/{network}/metadata/contracts Filtered contract metadata lookup by contract hash list.
GET /indexer/v1/networks/{network}/metadata/addresses Filtered address metadata lookup with tags, NNS metadata, and branding.

Recommended pattern: use /indexer/v1 for product-facing integrations, and jump to /rest/v1 only when you need table-level filters, projections, or raw explorer datasets.

REST Compatibility Tables

These worker paths expose indexed explorer-compatible tables and smart-contract intelligence through PostgREST query syntax.

Method Table / View Typical Usage
GET/rest/v1/blocksnetwork=eq.mainnet&limit=1
GET/rest/v1/transactionsnetwork=eq.mainnet&limit=1
GET/rest/v1/contractsnetwork=eq.mainnet&limit=1
GET/rest/v1/contract_eventsnetwork=eq.mainnet&contract_hash=eq.0x48c4...&event_name=eq.Transfer
GET/rest/v1/transaction_executionsnetwork=eq.mainnet&limit=1
GET/rest/v1/transaction_signersnetwork=eq.mainnet&txid=eq.0x...
GET/rest/v1/contract_notificationsnetwork=eq.mainnet&txid=eq.0x...
GET/rest/v1/nep17_transfersnetwork=eq.mainnet&txid=eq.0x...
GET/rest/v1/nep11_transfersnetwork=eq.mainnet&txid=eq.0x...
GET/rest/v1/indexer_statenetwork=eq.mainnet&select=network,last_indexed_block
GET/rest/v1/indexer_shard_statenetwork=eq.mainnet&shard_id=eq.mainnet-bf3

REST Views, Caches, and Utility Tables

These endpoints provide cached enrichment, portfolio views, analytics rollups, and application-level tables. Open /api for the full live schema, parameters, and response samples.

Method Table / View Typical Usage
GET/rest/v1/validator_metadata_cachenetwork=eq.mainnet&limit=10
GET/rest/v1/address_metadata_cachenetwork=eq.mainnet&limit=10
GET/rest/v1/contract_metadata_cachenetwork=eq.mainnet&limit=10
GET/rest/v1/v_account_overviewnetwork=eq.mainnet&limit=1
GET/rest/v1/v_account_contract_interactionsnetwork=eq.mainnet&limit=1
GET/rest/v1/v_contract_overviewnetwork=eq.mainnet&limit=1
GET/rest/v1/v_token_overviewnetwork=eq.mainnet&limit=1
GET/rest/v1/v_daily_chain_analyticsnetwork=eq.mainnet&limit=7
GET/rest/v1/v_nep17_balancesnetwork=eq.mainnet&limit=1
GET/rest/v1/address_tagslimit=20
GET/rest/v1/contract_metadatalimit=20
GET/rest/v1/multisig_requestslimit=20
GET/rest/v1/multisig_signatureslimit=20
GET/rest/v1/watchlistslimit=20

Schema rule: if a REST table or view appears on /api, it is coming from the live worker-exposed OpenAPI document at https://api.n3index.dev/rest/v1/.