API Reference Overview
The Chronary REST API provides programmatic access to API keys, calendars, events, availability, webhooks, and more.
OpenAPI Spec & Tooling
Section titled “OpenAPI Spec & Tooling”| Resource | URL |
|----------|-----|
| OpenAPI 3.1 spec | api.chronary.ai/openapi.json |
| LLM-friendly docs | docs.chronary.ai/llms.txt |
| Full LLM reference | docs.chronary.ai/llms-full.txt |
Import the OpenAPI spec into Postman, Insomnia, or any OpenAPI-compatible tool. Set {{base_url}} to https://api.chronary.ai and {{api_key}} to your key.
Base URL
Section titled “Base URL”https://api.chronary.ai/v1All endpoints are versioned under /v1/.
Authentication
Section titled “Authentication”Include your API key in the Authorization header:
Authorization: Bearer chr_sk_your_key_hereSee Authentication for details.
Request format
Section titled “Request format”- Content-Type:
application/jsonfor POST and PATCH requests - Query parameters: Used for GET requests (filtering, pagination)
- Path parameters: Resource IDs in the URL path
Response format
Section titled “Response format”All responses return JSON with consistent structure:
Single resource:
{ "id": "agt_a1b2c3d4", "name": "Sales Agent", "type": "ai", "status": "active", "created_at": "2026-04-04T12:00:00Z", "updated_at": "2026-04-04T12:00:00Z"}List response:
{ "data": [ ... ], "total": 42, "limit": 50, "offset": 0}Pagination
Section titled “Pagination”All list endpoints support limit and offset query parameters:
| Parameter | Type | Default | Range |
|-----------|------|---------|-------|
| limit | integer | 50 | 1–200 |
| offset | integer | 0 | 0+ |
Error responses
Section titled “Error responses”Errors follow a standard format:
{ "error": { "type": "not_found", "message": "Agent not found", "request_id": "req_abc123" }}See Error Codes for all error types.
Rate limits
Section titled “Rate limits”- 10 requests per second per API key
- Monthly API call quotas vary by plan
See Rate Limits for details.