CryptoBots Developer API

Your trading data.
Your dashboard.

Connect your own tools to the account, bot, performance, deal, and trade-event data you see in CryptoBots—through a secure, read-only API.

Start building See the reference
  • Read-only
  • 120 requests/min
  • OpenAPI 3.1

First request

Read-only 
curl https://api.cryptobots.io/api/v1/developer/events?limit=25 \
  -H "Authorization: Bearer $CBIO_API_KEY"

{
  "success": true,
  "data": {
    "items": [ ... ],
    "nextCursor": "..."
  }
}

CryptoBots Developer API

Connect your own tools to the account, bot, performance, deal, and trade-event data you see in CryptoBots—through a secure, read-only API.

One key, your data

Every key is tied to its owner. Requests cannot select or discover another user's records.

Dashboard-ready resources

List bots, pull normalized trade events, and read the same deal, profit, and performance views used by the web app.

Read-only by design

Scoped and revocable keys never reveal your exchange credentials and cannot place, stop, or change trades.

Quick start

From key to first response

  1. Sign in and open Developer API.
  2. Create and copy a key. It is shown once.
  3. Send it as a Bearer token over HTTPS.
  4. Follow nextCursor to load more events.
curl https://api.cryptobots.io/api/v1/developer/events?limit=25 \
  -H "Authorization: Bearer $CBIO_API_KEY"

API v1 reference

Read the data behind your trade view

GET /accountAccount identity and locale
GET /botsAll bots owned by the key's user
GET /bots/{botId}Opaque bot identity and lifecycle status only
GET /bots/{botId}/dealsDeals and latest orders shown in the web UI
GET /bots/{botId}/statsPerformance and ROI statistics
GET /bots/{botId}/profitsDaily profit history
GET /eventsFilterable, cursor-paginated trade events
GET /events/{eventId}One normalized trade event

Download the OpenAPI 3.1 specification →

Errors: 401 means the key is invalid, expired, or revoked; 403 means its scope is insufficient; 404 does not reveal whether an unowned resource exists; 429 means the 120-request-per-minute window has been exceeded.

Built for personal dashboards and agents

Stable JSON resources, explicit scopes, ISO timestamps, cursor pagination, predictable errors, and an OpenAPI contract make the API straightforward for applications and AI agents. Keep keys server-side, rotate them regularly, and revoke any key you no longer use.

Available resources: account, bot identity/status, allowlisted executed deals and orders, statistics, daily profits, and normalized trade events. Bot configuration, strategy parameters, provider IDs, and exchange credentials are never included.

Developer API questions