CallFire API Documentation

Name: CallFire API Documentation API
Brand: CallFire API Documentation
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsVoice Telephonybasic107 EndpointsREST

For Agents

Run text and voice broadcasts, build IVR campaigns, manage keywords and numbers, and subscribe to webhooks through this CallFire V2 API mirror.

Quickstart

Get started with CallFire API Documentation 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:
"send a text broadcast"

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

Capabilities

What an agent can do with CallFire API Documentation API.

Run text broadcasts with start, stop, and archive lifecycle controls via /campaigns/text-broadcasts

Run voice broadcasts via /campaigns/voice-broadcasts and recorded IVR campaigns via /campaigns/ivrs

Configure inbound automatic text replies via /campaigns/text-auto-replys

Lease and manage short-code keywords and phone numbers via the keyword-leases and number-leases endpoints

GET STARTED

Start building with CallFire API Documentation API

Explore with Jentic

View OpenAPI Document

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

This is a SwaggerHub-hosted mirror of the CallFire V2 API documentation, covering 107 operations across 73 paths. CallFire is a voice and SMS communications platform that supports text broadcasts, voice broadcasts, IVR campaigns, text auto-reply, keyword leasing, number leasing, contacts and lists, do-not-call (DNC) management, orders, subscriptions, and webhooks. Authentication is HTTP Basic with the API username and password issued in the CallFire dashboard. This spec is sourced from a third-party SwaggerHub maintainer rather than CallFire's own developer portal, so resource coverage is wider in places but version-tracking lags the vendor-official spec.

Use Cases

Patterns agents use CallFire API Documentation API for, with concrete tasks.

★ IVR Campaign with Branching

Build an interactive voice response campaign by POSTing to /campaigns/ivrs with the IVR tree definition, attaching recipients via /campaigns/ivrs/{id}/recipients, then starting the campaign with /campaigns/ivrs/{id}/start. Real-time call detail records are available through /campaigns/ivrs/{id}/calls and the campaign can be paused with the matching stop endpoint.

POST an IVR definition to /campaigns/ivrs, attach recipients, then POST to /campaigns/ivrs/{id}/start.

Inbound Auto-Reply on Keyword

Lease a keyword via /keyword-leases, then create an auto-reply with /campaigns/text-auto-replys so that any inbound text matching the keyword gets a templated response without an agent in the loop. This pattern is used for opt-in confirmations, voucher delivery, and event RSVPs.

Lease a keyword via /keyword-leases then POST a /campaigns/text-auto-replys entry that fires on that keyword.

Bulk SMS Broadcast with DNC Filtering

Before sending a marketing text broadcast, add suppressed numbers to the DNC list via the /dncs endpoints, then create a contact list, attach it to a /campaigns/text-broadcasts entry, and start the broadcast. CallFire automatically excludes DNC numbers, which keeps campaigns compliant with TCPA and similar opt-out rules.

POST DNC entries to /dncs, create the contact list, then POST a /campaigns/text-broadcasts entry and call start.

Phone Number Provisioning

Lease a new phone number via /number-leases for use in an outbound voice broadcast or as an inbound number that triggers IVR or auto-reply campaigns. The /numbers endpoints expose number metadata including capabilities (voice, SMS) so the agent can pick a suitable number programmatically before leasing.

Search /numbers for available US local numbers with SMS capability, then POST to /number-leases to lease the chosen number.

AI Agent Multi-Channel Outreach via Jentic

Through Jentic, an AI agent searches for an intent like 'send a text broadcast' and is returned the matching CallFire operation along with its input schema. Because CallFire uses HTTP Basic, Jentic stores both the username and password fragments in the credential vault and assembles the Authorization header at execution time. The agent can chain text broadcasts, voice broadcasts, and webhook subscriptions in a single workflow without writing direct API client code.

Use Jentic search for 'send a text broadcast', load the /campaigns/text-broadcasts schema, and execute it with the contact list and message body.

Key Endpoints

107 endpoints — this is a swaggerhub-hosted mirror of the callfire v2 api documentation, covering 107 operations across 73 paths.

METHOD

PATH

DESCRIPTION

POST

/campaigns/text-broadcasts

Create a text broadcast

POST

/campaigns/text-broadcasts/{id}/start

Start a text broadcast

POST

/campaigns/voice-broadcasts

Create a voice broadcast

POST

/campaigns/ivrs

Create an IVR campaign

POST

/campaigns/ivrs/{id}/start

Start an IVR campaign

POST

/campaigns/text-auto-replys

Configure inbound auto-reply

POST

/campaigns/sounds/tts

Generate a TTS sound

POST

/campaigns/text-broadcasts

Create a text broadcast

POST

/campaigns/text-broadcasts/{id}/start

Start a text broadcast

POST

/campaigns/voice-broadcasts

Create a voice broadcast

POST

/campaigns/ivrs

Create an IVR campaign

POST

/campaigns/ivrs/{id}/start

Start an IVR campaign

Why though Jentic?

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

Credential isolation

CallFire uses HTTP Basic. Jentic stores both the API username and password encrypted in the vault and constructs the Authorization header at execution time, so the agent never holds either credential fragment in its prompt or context.

Intent-based discovery

Agents search Jentic by intent (for example 'send a text broadcast' or 'set up auto reply') and Jentic returns the matching operation along with its input schema, so the agent can call the right endpoint without browsing the 73-path V2 reference.

Time to first call

Direct integration: 2-5 days for Basic auth wiring, broadcast and IVR lifecycle handling, and webhook receiver setup. Through Jentic: under 1 hour — search for the operation, load its schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

CallFire API

The vendor-official CallFire V2 spec covers the same platform; choose it when version recency matters more than the broader coverage of the SwaggerHub mirror.

Pick the vendor-official spec when you need the latest endpoints; pick this mirror only when an endpoint is missing from the vendor spec.

Complementary

CallerAPI

CallerAPI screens and enriches numbers; CallFire delivers the broadcast to those numbers.

Run CallerAPI checks first to filter destination lists, then send the cleaned list as a CallFire text or voice broadcast.

Complementary

Call Control API

Call Control flags spam-reported numbers; pair with CallFire to suppress those numbers via the DNC endpoints before sending.

Use Call Control to identify spam-reported destination numbers and POST them to /dncs before launching the broadcast.

FAQs

Specific to using CallFire API Documentation API through Jentic.

What authentication does this CallFire API mirror use?

It uses HTTP Basic authentication with the API username and password issued in the CallFire dashboard. The agent presents an Authorization header containing the base64-encoded credentials. Through Jentic, both fragments are held encrypted in the vault and only assembled at execution time.

Can I run an IVR campaign through this API?

Yes. POST an IVR definition to /campaigns/ivrs, attach recipients via /campaigns/ivrs/{id}/recipients, and start the campaign with /campaigns/ivrs/{id}/start. Lifecycle endpoints for stop and archive are also exposed.

How does this spec differ from the official CallFire spec?

This spec is a SwaggerHub-hosted mirror with 107 operations across 73 paths. It tends to lag the vendor-official spec on new endpoints, but includes broader resource coverage in some areas such as IVRs and keyword leases. Pick the vendor-official CallFire spec when version recency matters most.

What are the rate limits for this API?

Rate limits are not declared in the OpenAPI specification. CallFire enforces account-level throughput tied to your plan and dialer concurrency — review your CallFire dashboard before scheduling concurrent broadcasts.

How do I send a text broadcast through Jentic?

Run a Jentic search for 'send a text broadcast', load the /campaigns/text-broadcasts schema, and execute it with the contact list and message body. Then load and execute the start broadcast schema. Install the SDK with pip install jentic and use the async search, load, and execute pattern.

Is this API free to use?

CallFire prices on a per-minute and per-text basis with monthly plans, and the SwaggerHub mirror does not change the underlying billing. Check callfire.com for current rates and dashboard usage before launching a campaign.