Developers

API Documentation

Build powerful trading applications with the AetherNode REST and WebSocket APIs. Low-latency market data, order management, and account operations.

Overview

The AetherNode API provides programmatic access to our trading platform. All REST endpoints return JSON responses and accept JSON request bodies. Authentication uses HMAC-SHA256 signed requests with your API key and secret.

Base URL

https://api.aethernode.io/api/v1

WebSocket URL

wss://stream.aethernode.io/ws/v1

Endpoints

GET /api/v1/tickerPublic

Get real-time ticker data for a specific trading pair. Returns price, volume, and 24h statistics.

GET /api/v1/klinesPublic

Retrieve candlestick/kline data. Supports intervals from 1m to 1M. Maximum 1000 candles per request.

GET /api/v1/orderbookPublic

Get the current order book for a trading pair. Configurable depth (5, 10, 20, 50, 100 levels).

POST /api/v1/orderAuth

Place a new order (market, limit, stop-limit, trailing stop). Requires API key with trading permissions.

DELETE /api/v1/order/{id}Auth

Cancel an open order by ID. Supports bulk cancellation with the DELETE /api/v1/orders endpoint.

GET /api/v1/accountAuth

Retrieve account balances, positions, open orders, and margin information. Requires read permissions.

WS /ws/v1/streamWebSocket

WebSocket connection for real-time market data, order updates, and account events. Binary and JSON formats.

GET /api/v1/tradesPublic

Recent trades for a trading pair. Returns up to 1000 trades with price, quantity, and timestamp.

Rate Limits

Public Endpoints

1200 requests per minute per IP address. No authentication required for market data.

Authenticated Endpoints

2400 requests per minute per API key. Higher limits available for institutional accounts.

WebSocket Connections

5 concurrent connections per API key. Each connection supports up to 200 stream subscriptions.

Order Placement

10 orders per second per account. Burst of up to 50 orders allowed with cooldown period.

Authentication

Generate API keys from your account settings. Each key has configurable permissions (read, trade, withdraw). All authenticated requests require three headers: X-API-KEY, X-API-SIGN (HMAC-SHA256), and X-API-TIMESTAMP.

Example Request Header

X-API-KEY: your_api_key
X-API-SIGN: hmac_sha256(secret, timestamp + method + path + body)
X-API-TIMESTAMP: 1708963200000