API Tokens
API access tokens authenticate requests to the Veronese JSON API. Each token is a long random string used as a Bearer token in the Authorization header.
Endpoints
Section titled “Endpoints”List tokens
Section titled “List tokens”GET /api_access_tokens.jsonReturns all active tokens for the authenticated user. Token values are not included in list responses.
Example response:
{ "success": true, "api_access_tokens": [ { "id": "tok_123", "name": "My CLI token", "last_used_at": "2026-03-20T10:00:00Z", "created_at": "2026-01-01T00:00:00Z" } ]}Create token
Section titled “Create token”POST /api_access_tokens.jsonCreates a new token. The plain token value is returned only in this response and cannot be retrieved again.
Request:
{ "api_access_token": { "name": "My CLI token" }}Response:
{ "success": true, "api_access_token": { "id": "tok_123", "name": "My CLI token", "token": "vero_live_xxxxxxxxxxx", "created_at": "2026-03-20T00:00:00Z" }}Copy and store this token immediately — it cannot be shown again.
Delete token
Section titled “Delete token”DELETE /api_access_tokens/:id.jsonImmediately revokes the token. Any in-flight or future requests using it will return 401.
Response:
{ "success": true}