CCCryptoContext Docs
REST API

REST API

Authentication, replies, errors and limits of the REST API.

Base URL: https://api.cccontext.com. Every MCP tool is POST /v1/tools/<name>; see Endpoints and the REST quickstart. The OpenAPI document is at https://api.cccontext.com/v1/openapi.json.

Authentication

  • x-api-key: <access token> on each request, or
  • Authorization: Bearer <JWT>, where the JWT comes from POST https://gateway.cccontext.com/api/token with {"access_token": "<token>"} and is valid for one hour.

A token belongs to one connection; every call acts on that connection.

Replies and errors

{ "ok": true, "result": { } }
{ "ok": false, "error": { "code": "LIQUIDATION_BEFORE_STOP", "message": "…", "retryable": false } }

Error codes are stable. retryable: true means the same request may succeed later; RATE_LIMITED replies carry retry-after. OUTCOME_UNKNOWN (HTTP 409) means the exchange did not confirm the result: read your orders and positions before you retry.

Limits

Requests per minute depend on your plan (see plans) and count every request your account makes, across connections. Mutating requests are idempotent within a short window, and you can pass your own idempotency_key to make retries safe.

On this page