Introduction
The CryptoExchange Pro API is organized around REST principles. It has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
Our API supports the following features:
- Market Data: Real-time prices, order books, and historical candles.
- Account Management: Balances, profile information, transaction history.
- Trading: Place, modify, and cancel orders programmatically.
- P2P & Agents: Access P2P order books and agent information.
- Webhooks: Receive real-time notifications for events.
https://api.cryptoprox.com/v1Authentication
The CryptoExchange Pro API uses API keys to authenticate requests. You can generate your API keys from your Profile page under the "API Management" section.
Each API key consists of two parts:
- API Key (Public): Included in every request to identify your account.
- API Secret (Private): Used to sign requests. Never share this with anyone.
Authentication Header: Include your API key in the X-API-KEY header of every request:
For endpoints that require authentication, requests without valid credentials will return a 401 Unauthorized response.
Base URL & Environments
We provide two environments for your integration:
| Environment | Base URL | Purpose |
|---|---|---|
| Production | https://api.cryptoprox.com/v1 |
Live trading with real funds |
| Sandbox | https://sandbox-api.cryptoprox.com/v1 |
Testing with simulated funds |
Rate Limits
To ensure fair usage and stability for all users, we enforce the following rate limits:
Rate limit headers are included in every response:
429 Too Many Requests response. Wait until the X-RateLimit-Reset timestamp before retrying.API Endpoints
Below is a complete reference of all available endpoints. Click any endpoint to see detailed parameters, examples, and responses.
| Parameter | Type | Required | Description |
|---|---|---|---|
| order_type | string |
Yes | "buy" or "sell" |
| symbol | string |
Yes | Trading pair (e.g., "BTC/USDT") |
| price | number |
Yes | Price per unit in USDT |
| amount | number |
Yes | Quantity to buy/sell |
| trader_id | integer |
No | P2P trader ID (optional) |
Webhooks
Webhooks allow you to receive real-time notifications when events happen on your account. Instead of polling the API, you can configure a URL and we'll send an HTTP POST request whenever an event occurs.
Supported Events:
- order.filled — An order has been fully executed.
- order.cancelled — An order has been cancelled.
- withdrawal.completed — A withdrawal has been processed.
- withdrawal.rejected — A withdrawal has been rejected.
- deposit.confirmed — A crypto deposit has been credited.
Configure your webhook URL in your Profile settings. We'll retry failed deliveries up to 5 times with exponential backoff.
Error Codes
The API uses standard HTTP status codes to indicate the success or failure of a request. In case of an error, the response body will contain additional information.
Bad Request
The request was malformed or missing required parameters.
Unauthorized
Missing or invalid API credentials.
Forbidden
Your API key doesn't have permission for this action.
Not Found
The requested resource does not exist.
Rate Limited
You've exceeded the rate limit. Wait before retrying.
Internal Error
Something went wrong on our end. Try again later.
SDKs & Libraries
To speed up your integration, we provide official SDKs for popular programming languages:
| Language | Package | Install |
|---|---|---|
| JavaScript / Node.js | @cryptoprox/sdk |
npm install @cryptoprox/sdk |
| Python | cryptoprox |
pip install cryptoprox |
| PHP | cryptoprox/php-sdk |
composer require cryptoprox/php-sdk |
| Go | go-cryptoprox |
go get github.com/cryptoprox/go-sdk |
Developer Support
Need help integrating with our API? Our developer support team is here to assist you:
- Email: api@cryptoprox.com
- GitHub: github.com/cryptoprox — Report issues, contribute examples
- Discord: Join our #developers channel for real-time help
- Status Page: status.cryptoprox.com — API uptime and incidents
X-Request-ID header from your API response for faster debugging.