Skip to content
API Reference

Search is only available in production builds. Try building and previewing the site to test it out locally.

Environments & Chains

The hosts behind the Proxima API, and the chain and network identifiers used in request paths.

Proxima runs as a set of services. The REST API carries almost every operation; dedicated hosts serve realtime channels, the market datafeed, images and support tickets.

Hosts

ServiceProductionDevelopment
REST APIhttps://api-mig.proxima.toolshttps://api.proximatool.dev
Realtime channels (Centrifugo)wss://ws.proxima.tools/connection/websocketwss://ws.proximatool.dev/connection/websocket
Market datafeedwss://datafeed.proxima.tools/wswss://datafeed.proximatool.dev/ws
Datafeed HTTPhttps://datafeed.proxima.toolshttps://datafeed.proximatool.dev
Image proxyhttps://img.proxima.toolsProduction only
Support ticketshttps://support-api.proxima.toolsProduction only

A second production API, https://api-prod-update.proxima.tools, is used to stage releases. It runs alongside the same production realtime and datafeed hosts. Use it only when Proxima asks you to verify a release.

Every REST path in this reference is relative to the API base URL. Examples use production:

Terminal window
export PROXIMA_API=https://api-mig.proxima.tools
curl "$PROXIMA_API/health"

Chains

Endpoints that act on a single chain take its identifier in the path, usually as {chain_id}. The identifiers are stable lowercase strings:

chain_idChainnetwork_typeNative assetBase units per native unitStatus
solSolanasvmSOL1000000000 (10⁹)Live
ethEthereumevmETH1000000000000000000 (10¹⁸)Live
bscBNB Smart ChainevmBNB1000000000000000000 (10¹⁸)Live
baseBaseevmETH1000000000000000000 (10¹⁸)Live
robinhoodRobinhoodevmETH1000000000000000000 (10¹⁸)Live
arcArcevmUSDC1000000000000000000 (10¹⁸)Live
xlayerX LayerevmOKB1000000000000000000 (10¹⁸)Live
monadMonadevmMON1000000000000000000 (10¹⁸)Not live

The table reflects the platform constants at the time of writing. Read GET /get-constants at startup instead of hard-coding it: the response lists every chain with its live flag, native symbol, known tokens, dust and minimum balance thresholds, the launchpads and DEXs it supports (dexs) and the features enabled on it (features).

Network types

Wallets are created per virtual machine rather than per chain: an EVM wallet holds the same address on Ethereum, BSC, Base and every other EVM chain. Wallet endpoints therefore take a {network_type} path segment:

network_typeVirtual machineChains
svmSolana Virtual Machinesol
evmEthereum Virtual Machineeth, bsc, base, robinhood, arc, xlayer, monad

Rule of thumb: wallet creation and imports are scoped by network_type; anything that sends a transaction, reads a balance on a specific chain or targets a launchpad is scoped by chain_id.

POST /wallets/evm/add # one EVM wallet, usable on every EVM chain
POST /launch/bsc/import-mint # import a token that lives on BSC
GET /sol/shield/get-shield-info # Shield state on Solana

Health check

GET /health needs no authentication. Use it to check reachability and to measure clock drift: ts is the server time in epoch milliseconds.

{ "ok": true, "ts": 1767225600000 }

The public status page at status.proxima.tools reports incidents and maintenance windows.