Developer API

API Documentation

Integrate with CryptoX using our comprehensive REST and WebSocket APIs

Overview

REST API

Standard HTTP endpoints for trading, account management, and market data retrieval.

WebSocket

Real-time streaming for order book updates, trades, and ticker data.

Rate Limits

Up to 20 requests per second for REST API with fair usage policies.

Quick Start

Get started with a simple API request. Copy the example below to fetch market data.

JavaScript

const response = await fetch(
  "https://api.cryptox.com/v1/market/ticker?symbol=BTC_USDT",
  {
    headers: {
      "X-API-Key": "your-api-key",
      "X-Timestamp": Date.now().toString(),
      "X-Signature": signature,
    },
  }
);

const data = await response.json();
// { success: true, data: { price: "67430.50", ... } }

API Endpoints

Explore our available API categories and endpoints

Market Data

Ticker, order book, recent trades, and K-line data

GET /v1/market/ticker

GET /v1/market/depth

GET /v1/market/trades

Trading

Place orders, cancel orders, and view order history

POST /v1/order/place

DELETE /v1/order/cancel

GET /v1/order/history

Account

Balances, deposit/withdrawal, and transaction history

GET /v1/account/balance

POST /v1/account/withdraw

GET /v1/account/transactions

WebSocket

Real-time market data and order update streams

ws://ticker@btc_usdt

ws://depth@btc_usdt

ws://trades@btc_usdt

Rate Limiting

API rate limits ensure fair usage for all users

Tier	Rate Limit	Time Window
Public	20 req/s	Per second
Authenticated	50 req/s	Per second
Trading	10 req/s	Per second
WebSocket	5 connections	Per user

Authentication

Secure your API access with API keys and request signing

API Key Setup

Follow these steps to authenticate your API requests.

1Generate an API key pair in your account settings

2Sign each request using HMAC-SHA256 with your secret key

3Include X-API-Key, X-Timestamp, and X-Signature headers

4Handle response status codes and error messages

Security Best Practices

Follow these tips to keep your API keys secure.

Enable IP whitelist to restrict API access to trusted addresses

Use the principle of least privilege when setting key permissions

Rotate your API keys regularly (recommended: every 90 days)

Never share your API secret key or commit it to source code