Everything starts with two things: the base URL and an API token. This chapter gets you from zero to your first successful request.

All API endpoints are prefixed with /api/v1.

• An API authentication token (request from support@everycallhandled.com, or mint a scoped key yourself — see API Keys)
• An HTTPS client capable of REST API calls
• JSON request/response handling

• All timestamps are ISO 8601 (e.g. "2026-05-10T12:00:00Z").
• Boolean attributes on apps are stored as strings ("true" / "false"). Where this affects your client, the docs call it out explicitly.
• Standard HTTP status codes (200/400/401/403/404/409/429/500); error bodies are nested under err: { "err": { "message": "<message>", "code": "<symbolic_code>" } } (code defaults to INTERNAL_ERROR).
• API tokens are long-lived credentials — store securely, rotate periodically.
• Asynchronous operations (knowledge ingestion, taking an assistant live) return immediately; you poll for completion.

Email support@everycallhandled.com for a token, or mint a capability-scoped key yourself once you have dashboard access (see API Keys). Keep tokens out of client-side code and version control; store them in environment variables or a secrets manager. Contact support immediately if you suspect a token has been compromised.

Include your token in the Authorization header on every request:

List the apps in your account:

A 200 with a JSON body means you're authenticated and ready to build. A 401 means the token is missing or invalid.

Every token acts as a member of your account, with a role and a set of permissions (features). The role sets a baseline; per-user overrides fine-tune it. When an endpoint needs a specific permission, its documentation says so — for example Requires `edit_settings` . Endpoints with no permission noted are available to any signed-in member of the account that owns the app.

Tokens issued by support come pre-configured with the permissions your integration needs. The full permission catalogue and role baselines are in Your Team — Roles & Permissions.