Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cronozen.com/llms.txt

Use this file to discover all available pages before exploring further.

​
API Reference

​
Base URL

Production: https://cronozen.com/api
Staging:    https://stg.cronozen.com/api

​
Authentication

The Cronozen platform supports two authentication methods:

​
JWT Token (Platform APIs)

All platform API calls require a JWT token in the Authorization header: 
Authorization: Bearer <jwt-token>
See Authentication for details on obtaining tokens.

​
API Key (Proof API)

The Proof API uses API key authentication with scoped permissions: 
Authorization: Bearer czk_live_abc123...
ScopePermissions
proof:readQuery events, get evidence, export reports
proof:writeRecord events, add approvals (includes read)
See Proof API for details.

​
API Groups

GroupPrefixAuthDescription
Auth/api/auth/*JWTLogin, session, token management
Centers/api/centers/*JWTCenter CRUD and management
Workspace/api/workspace/*JWTPersonal workspace operations
Schedules/api/schedules/*JWTUnified scheduling across verticals
Partner/api/partner/*JWTPartner platform management
Workflows/api/workflows/*JWTAI automation workflows
Proof/v1/decision-events/*API KeyDecision evidence recording and export
Cron/api/cron/*InternalScheduled tasks
The Proof API uses API key authentication instead of JWT. See Proof API Reference.

​
Response Format

All responses follow a consistent format: 
{
  "success": true,
  "data": { ... },
  "error": null
}
Error responses: 
{
  "success": false,
  "data": null,
  "error": {
    "code": "UNAUTHORIZED",
    "message": "Invalid or expired token"
  }
}

​
Rate Limiting

API calls are rate-limited per actor:
TierLimit
Standard100 req/min
Partner500 req/min
InternalUnlimited

​
Tenant Scoping

All API responses are automatically scoped to the authenticated actor’s current center. Cross-center queries are only available through specific endpoints with proper authorization.
Never pass center_id as a query parameter for data access. The center context is derived from the JWT token.