Skip to main content
AGENTS.md encodes the non-obvious facts and gotchas an AI coding assistant needs to generate correct Bolna API code — the things most likely to produce broken code if missed. The OpenAPI spec is the authoritative reference; AGENTS.md surfaces what it’s easy to miss.

Highlights

Base URL:  https://api.bolna.ai
Auth:      Authorization: Bearer <api_key>
A missing or invalid key returns 401 Access denied.
Both return 201 Created. The agent-create response field is state, not status. The legacy v1 /agent endpoint returns 200 — only v2 returns 201.
A trailing Z for UTC is rejected with a 500 error. Use a numeric offset instead, e.g. 2026-06-23T15:30:00+00:00. Scheduling must also be at least 2 minutes in the future, and Bolna rounds up to the next 10-minute mark.
call-disconnected fires the instant the line drops — at that moment conversation_duration, total_cost, recording_url, and extracted_data are still null or 0. The completed event arrives a few seconds later with all fields populated.
Not an array of strings. Correct shape: "pipelines": [["transcriber", "llm", "synthesizer"]].
Not wrapped in { "data": [...] } — the response is the array directly.
Bolna sends webhooks from 13.203.39.153. Whitelist this IP or events will be dropped.

What else is in the file

  • The full execution status lifecycle (queued → initiated → ringing → in-progress → call-disconnected → completed, plus terminal states)
  • The batch status lifecycle
  • A minimal working agent creation body
  • A key endpoint summary table
Read the complete file at /AGENTS.md.