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

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 buildingEvery key is tied to its owner. Requests cannot select or discover another user's records.
List bots, pull normalized trade events, and read the same deal, profit, and performance views used by the web app.
Scoped and revocable keys never reveal your exchange credentials and cannot place, stop, or change trades.
nextCursor to load more events.curl https://api.cryptobots.io/api/v1/developer/events?limit=25 \
-H "Authorization: Bearer $CBIO_API_KEY"
{
"success": true,
"data": {
"items": [ ... ],
"nextCursor": "..."
}
}GET /account | Account identity and locale |
GET /bots | All bots owned by the key's user |
GET /bots/{botId} | Opaque bot identity and lifecycle status only |
GET /bots/{botId}/deals | Deals and latest orders shown in the web UI |
GET /bots/{botId}/stats | Performance and ROI statistics |
GET /bots/{botId}/profits | Daily profit history |
GET /events | Filterable, cursor-paginated trade events |
GET /events/{eventId} | One normalized trade event |
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.
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.