API Documentation

Authentication & Security

Supported methods. Use API Key + Secret for most integrations. For access to Production, Sandbox and WebSocket endpoints contact our developer team.

Headers:
X-API-KEY: your_api_key_here
X-API-SECRET: your_api_secret_here
X-TIMESTAMP: 1699123456789
X-SIGNATURE: HMAC-SHA256(timestamp + method + path + body)

Request access: Email dev@trade360.ai to request Production, Sandbox or WebSocket credentials.

Base URLs & Rate Limits

Rate limits

Market Data

GET /market/live · GET /market/depth · GET /market/historical

Trading

POST /orders/place (most important)

{
  "exchange": "MCX",
  "symbol": "GOLDM25NOVFUT",
  "transaction": "BUY",
  "type": "MARKET",
  "quantity": 2,
  "product": "MARGIN",
  "validity": "DAY"
}

If you need example account credentials or sandbox tokens for testing, email dev@trade360.ai.

Webhooks & WebSocket

Register webhook and validate HMAC-SHA256 signature on receipt.

POST /webhooks/register
{
  "url":"https://yourserver.com/webhook",
  "events":["order.executed","order.rejected"],
  "secret":"your_webhook_secret"
}

WebSocket connection details are provided upon request. Email dev@trade360.ai.

Error Codes

Code Examples

// Use HMAC-SHA256 signature with timestamp + method + path + body
// See full SDK examples in original doc. For access to SDKs contact dev@trade360.ai

Best Practices

• Keep API secrets out of source control.
• Implement retries with backoff for rate limits.
• Use HTTPS and rotate keys periodically.