Bolna API

Name: Bolna API
Brand: Bolna API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsVoice Telephonybearer11 EndpointsREST

For Agents

Create voice AI agents, place outbound calls, run batch calling campaigns, and attach knowledge bases through Bolna.

Install Jentic One Beta

Connect the Bolna API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bolna API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Bolna API.

Create a voice AI agent with a configured prompt, voice, and language

Place an outbound call from a configured agent to a target phone number

Stop a running call mid-execution and retrieve its execution details afterwards

GET STARTED

Start building with Bolna API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Bolna API, keeping it validated and agent-ready. Bolna is a Voice AI platform that helps companies scale outbound and inbound calling by building intelligent voice agents trained on their own CRM and CMS data. The API exposes voice agent CRUD, outbound call initiation, batch campaigns, knowledge bases, and phone number search. Use it to spin up a new voice agent, place a call, monitor the execution, and attach a knowledge base so the agent can answer domain-specific questions live on the call.

Use Cases

Patterns agents use Bolna API for, with concrete tasks.

★ Outbound Lead Qualification at Scale

Automate the first call to inbound marketing leads using a Bolna voice agent that asks qualifying questions and books a meeting. POST /batches creates the campaign, POST /call places individual outbound calls, and GET /executions/{execution_id} returns the resulting transcript. Removes the cost of an SDR team running first-touch dials.

POST /batches with 500 lead phone numbers and agent_id agt_88, then poll GET /executions/{execution_id} for each call

Knowledge-Grounded Customer Support Voice Agent

Attach a product knowledge base to a Bolna voice agent so it answers customer support calls with grounded, up-to-date information instead of hallucinated responses. POST /knowledgebase ingests the source content, then PUT /v2/agent/{agent_id} associates it with the agent. Useful for tier-1 support deflection without hiring more agents.

POST /knowledgebase with the product docs, then PUT /v2/agent/agt_42 to attach the new knowledge_base_id

On-Demand Outbound Call Triggers

Trigger a single voice call from a workflow when a high-value event happens — for example, a churned customer reactivation or a delivery failure. POST /call with the agent ID and phone number returns an execution ID, and POST /call/{execution_id}/stop ends the call early if needed. Pairs well with CRM and webhook automations.

POST /call with agent_id agt_42 and phone +14155550100 to reach the customer about their failed delivery

AI Agent Voice Operations Layer

An AI agent uses Jentic to discover Bolna operations, creates voice sub-agents on demand, and places calls in response to upstream signals from CRM and ticketing systems. Bearer credentials live in the Jentic vault so they never enter the calling agent's prompt. Replaces a multi-day Twilio + LLM + telephony stack with a single search-load-execute cycle.

Search Jentic for 'place an outbound voice call', load the operation, and execute it for the assigned phone number

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for bolna api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v2/agent

Create a Voice AI agent

GET

/v2/agent/all

List all Voice AI agents

PUT

/v2/agent/{agent_id}

Update an agent

POST

/call

Initiate an outbound voice call

POST

/call/{execution_id}/stop

Stop a call in progress

GET

/executions/{execution_id}

Retrieve execution details

POST

/batches

Create a batch calling campaign

POST

/knowledgebase

Create a knowledge base

POST

/v2/agent

Create a Voice AI agent

GET

/v2/agent/all

List all Voice AI agents

PUT

/v2/agent/{agent_id}

Update an agent

POST

/call

Initiate an outbound voice call

POST

/call/{execution_id}/stop

Stop a call in progress

GET

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Bolna bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped, short-lived access tokens — the long-lived Bolna API key never enters the agent context or logs.

Intent-based discovery

Agents search Jentic with intents like 'place an outbound voice call' or 'create a voice AI agent' and Jentic returns the matching Bolna operation with its input schema, removing the need to read the Bolna reference.

Time to first call

Direct Bolna integration: 2-4 days to wire up auth, agent configuration, batch campaigns, and execution polling. Through Jentic: under an hour with search, load, and execute.

FAQs

Specific to using Bolna API through Jentic.

Why is there no official OpenAPI spec for Bolna API?

Bolna does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Bolna API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Bolna API use?

Bolna uses HTTP Bearer authentication — send Authorization: Bearer <token> on every request. Through Jentic the token is held in the encrypted vault and the agent only ever sees a scoped, short-lived bearer.

Can I place an outbound call with the Bolna API?

Yes. POST /call with the agent_id and the destination phone number. The response returns an execution_id you can use to monitor the call via GET /executions/{execution_id} or stop it with POST /call/{execution_id}/stop.

How do I run a batch calling campaign through Jentic?

Search Jentic for 'create a batch calling campaign', load the POST /batches operation schema, then execute it with the agent_id and the list of phone numbers. Monitor progress through the executions endpoint.

What are the rate limits for the Bolna API?

The OpenAPI spec does not declare formal rate limits. Voice calling is naturally rate-shaped by available phone capacity — use POST /batches for high-volume campaigns rather than fanning out individual /call requests.

Can I attach a knowledge base to a Bolna voice agent?

Yes. POST /knowledgebase to ingest your source content, then PUT /v2/agent/{agent_id} to associate the resulting knowledge_base_id with the agent. The agent will reference it during calls to ground responses.

Bolna API

Connect the Bolna API to your agent

Capabilities

Start building with Bolna API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs