Skip to main content

Introduction

Welcome to the Angstrom API Documentation. The API provides programmatic access to the Angstrom exchange.

Network Overview​

Because the Angstrom network is decentralized, there isn’t a single, central API server. Instead, each node in our network runs its own JSON‑RPC server.

Each Angstrom node runs its own JSON-RPC server—there is no single central API. For convenience and to ensure high availability, we provide a load-balanced endpoint that automatically distributes requests across multiple nodes.

Ideal for most users. Simple, resilient, and automatically distributes traffic.

  • HTTPS: https://mainnet.node-lb.backend.angstrom.xyz:8545
  • WebSocket: wss://mainnet.node-lb.backend.angstrom.xyz:8546

Direct Node Endpoints (Low Latency)​

For lowest possible latency, connect directly to individual nodes:

HTTPS:

  • https://mainnet.node1.backend.angstrom.xyz
  • https://mainnet.node2.backend.angstrom.xyz
  • https://mainnet.node3.backend.angstrom.xyz

WebSocket:

Note: These endpoints are experimental. Use the load balancer WS until they stabilize.

  • wss://ws.mainnet.node1.backend.angstrom.xyz
  • wss://ws.mainnet.node2.backend.angstrom.xyz
  • wss://ws.mainnet.node3.backend.angstrom.xyz

Data Endpoint​

To reduce node RPC load, endpoints that depend exclusively on on-chain state are exposed via our separate Data API—alternatively, you can fetch the same data yourself using on-chain calls in our SDK.

  • https://mainnet.node.data.angstrom.xyz

API Endpoint Categories​

Our API documentation is organized into logical sections based on functionality. While the following categories give you an overview of the available functionality, you can explore each section in detail using the sidebar navigation:

  • Trading Endpoints: Manage orders—including submission, cancellation, status updates, and retrieval.
  • Gas Estimation Endpoints: Obtain gas estimates for trades.
  • WebSocket Streams: Subscribe to live order updates based on your specified filters.
  • Exchange Endpoints : Retrieve core exchange metadata—supported token pairs, token registry, pool keys/identifiers, and on-chain pool configuration.
  • Liquidity Endpoints: Query user liquidity positions—fetch all positions held by an address or filter to positions within a specific pool.
note

The Exchange and Liquidity endpoints are only available via the data endpoint.