Overview
Last updated
Was this helpful?
Production
https://api.tokenbot.com/v1
Development
https://api-dev.tokenbot.com/v1
Endpoints are also reachable without the /v1 prefix as legacy aliases, but new integrations should use /v1.
Most endpoints require authentication. The primary method is an API key via the X-API-Key header (or Authorization: Bearer <key>). The tokenbot CLI uses signed requests as a fast-path. See Authentication.
A handful of endpoints are public (no auth): GET /v1/health, GET /v1/health/detailed, GET /v1/version, and GET /v1/auth/cli-challenge.
List endpoints support pagination:
limit
integer
20
Items per page (max 100)
offset
integer
0
Number of items to skip
sort
string
Field to sort by
order
string
asc or desc
Version
/v1/version
—
CLI identity
/v1/auth/cli-challenge, /v1/auth/cli-identity
—
The
/v1/trading-bot/*and/v1/market-maker/*proxy namespaces have been removed (rest-api #121). They forwarded to dashboard-era bot HTTP surfaces that were never wired up in any deployed environment — every call returned503— and those bot-side APIs are gone too (trading-bot #121, market-maker-bot #132). The embedded operator CLIs (tokenbot-trading,tokenbot-mm) now talk to the platform APIs directly: this REST API plus GraphQL atgql-api.tokenbot.com, with real-time data over thetradeSignalandorderbookUpdatesubscriptions. Remote bot control (pause / emergency-stop) returns in a future signed control-plane wave.
GET /v1/healthBasic health check (public).
GET /v1/health/detailedDetailed health check with service status (public).
GET /v1/meReturns the authenticated user's profile.
Last updated
Was this helpful?
Was this helpful?
curl https://api.tokenbot.com/v1/me \
-H "X-API-Key: tb_live_your_key"
