Bland AI API

Name: Bland AI API API
Brand: Bland AI API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsVoice Telephonybearer42 EndpointsREST

For Agents

Place programmatic outbound phone calls with conversational AI agents, manage call pathways and knowledge bases, send SMS, and analyse call recordings and transcripts.

Quickstart

Get started with Bland AI API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"place an AI phone call to a customer"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Bland AI API API.

Place an outbound AI phone call with a configured agent and pathway

Stop, list, and inspect calls in flight, including recordings and corrected transcripts

Run batch calling campaigns with /batches and stop them mid-flight

Configure conversational agents, pathways, voices, personas, and knowledge bases

GET STARTED

Start building with Bland AI API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Bland AI API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Bland AI API, keeping it validated and agent-ready. The Bland AI API powers programmatic phone calls and conversational voice AI: place outbound calls, run them through configured agents and pathways, capture recordings and transcripts, and analyse call outcomes after the fact. The spec also covers batch calling, inbound number purchasing, voices and personas, knowledge bases, custom tools that an agent can call mid-conversation, contact management, SMS, and blocked-number controls. It is the full stack for building AI voice agents that can hold a real phone conversation.

Use Cases

Patterns agents use Bland AI API API for, with concrete tasks.

★ AI Outbound Calling Campaign

Run an outbound calling campaign that places personalised AI phone calls to a contact list and routes responses through a configured pathway. POST /batches creates the campaign, GET /batches/{batchId} reports progress, and GET /calls/{callId}/recording plus POST /calls/{callId}/analyze surface the outcome of each call. The same flow is reused for appointment reminders, lead qualification, and customer outreach.

POST /batches with the contact list and target pathway, poll GET /batches/{batchId} until complete, then call POST /calls/{callId}/analyze on each call and report the outcomes.

Live Conversational Voice Agent

Build a conversational voice agent that can hold an open-ended phone call: configure the agent via POST /agents, attach knowledge through /knowledge/learn/text or /knowledge/learn/web, and define tools the agent can invoke mid-call via POST /tools. When a call is placed with POST /calls, the agent uses the pathway and tools to answer questions, take actions, and follow up with SMS via POST /sms/send.

POST /agents to create the agent, POST /knowledge/learn/text to attach the FAQ, POST /tools to expose a CRM lookup, then POST /calls to place a call routed through the agent.

Post-Call Analysis and Transcript Review

After a call completes, pull the recording and corrected transcript to feed into QA, compliance review, or downstream analytics. GET /calls/{callId}/recording returns the audio, GET /calls/corrected-transcript returns the cleaned transcript, and POST /calls/{callId}/analyze produces structured outcome metadata. This loop turns Bland AI calls into a measurable funnel.

Call POST /calls/{callId}/analyze for each completed call, then GET /calls/corrected-transcript and store both in the QA database.

Inbound Number Setup and Routing

Provision a Bland AI inbound number to receive calls, attach a pathway and agent, and route the inbound conversation accordingly. POST /inbound/purchase buys the number, GET /inbound lists provisioned numbers, and the pathway+agent endpoints define how the inbound call is handled. This is the foundation for AI-handled inbound support, sales, or appointment lines.

Call POST /inbound/purchase to acquire a number, then POST /agents with the inbound pathway id so calls to the number are routed through the configured agent.

Agent-Driven Call Through Jentic

An AI orchestrator agent decides the user needs a call rather than an email. It searches Jentic for 'place an AI phone call', loads the POST /calls schema, and executes the call with the supplied phone number and prompt. Bland AI bearer credentials remain in the Jentic vault, so the orchestrator never sees the raw API key. This makes Bland AI a drop-in voice tool for higher-level agent workflows.

Use Jentic search for 'place an AI phone call to a customer', load the POST /calls schema, then execute it with the phone number, agent id, and call prompt.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/calls

Place an AI phone call

GET

/calls/{callId}

Get call details

POST

/calls/{callId}/analyze

Analyze a completed call

POST

/batches

Create a batch calling campaign

POST

/agents

Create a conversational agent

POST

/knowledge/learn/text

Add text to a knowledge base

POST

/sms/send

Send a single SMS

POST

/inbound/purchase

Purchase an inbound number

POST

/calls

Place an AI phone call

GET

/calls/{callId}

Get call details

POST

/calls/{callId}/analyze

Analyze a completed call

POST

/batches

Create a batch calling campaign

POST

/agents

Create a conversational agent

POST

Why though Jentic?

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

Credential isolation

Bland AI uses a bearer API key. Jentic stores the key in the encrypted vault and exposes only a scoped Jentic token to the agent — important because the same key authorises outbound calls, SMS, and inbound number purchases that incur real charges.

Intent-based discovery

Agents search Jentic with intents like 'place an AI phone call to a customer' or 'send an SMS through Bland AI' and Jentic returns the matching operation from the 42-endpoint spec with its input schema.

Time to first call

Direct integration: 2-4 days to wire bearer auth, agent and pathway configuration, batch polling, and post-call analysis. Through Jentic: a few hours — search the operation, load schema, execute against /calls or /sms/send.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

BizToc

BizToc supplies news context that a Bland AI agent could read aloud during a call.

Pair them when an AI calling agent needs fresh news content as part of the conversation.

Complementary

Blastable

Blastable handles email blasts while Bland AI handles voice and SMS — useful as a multi-channel outreach pair.

Use Blastable for the email leg of a campaign and Bland AI for the voice/SMS leg.

Complementary

Blackfire API

Blackfire profiles the orchestrator service that drives Bland AI calls so the calling pipeline stays responsive.

Use Blackfire when a Bland AI orchestrator service needs latency or memory profiling.

FAQs

Specific to using Bland AI API API through Jentic.

Why is there no official OpenAPI spec for Bland AI API?

Bland AI does not publish an OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call Bland AI 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 Bland AI API use?

HTTP bearer authentication (security scheme bearerAuth). Callers attach a bearer token in the Authorization header. Through Jentic the token is stored in the encrypted vault, and the agent only ever sees a scoped Jentic token, not the raw Bland AI API key.

Can I place an AI phone call with the Bland AI API?

Yes. POST /calls is the entry point — supply the phone number, the agent id (or inline configuration), and the call task. Use GET /calls/{callId} to follow status and POST /calls/{callId}/stop to halt a call early.

How do I get the recording and transcript for a completed call?

Call GET /calls/{callId}/recording for the audio file and GET /calls/corrected-transcript for the cleaned transcript. POST /calls/{callId}/analyze returns structured outcome metadata you can store alongside the recording.

What are the rate limits for the Bland AI API?

The OpenAPI spec does not declare an explicit rate limit. Bland AI publishes per-account concurrency limits that scale with plan; design batch calling and SMS workflows to back off on HTTP 429 responses and respect the published per-minute quotas on your tier.

How do I place a Bland AI call through Jentic?

Install with pip install jentic, then use Jentic search with 'place an AI phone call to a customer'. Jentic loads the POST /calls schema; execute it with the phone number, agent id, and prompt. The bearer token never enters the agent's prompt context.

Is the Bland AI API free?

No. Bland AI is paid per minute of call time and per SMS, with rates published on the Bland AI website. There is no free tier in the API; account funding is required before /calls and /sms/send will succeed.