Callingly API

Name: Callingly API API
Brand: Callingly API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsVoice Telephonybearer31 EndpointsREST

For Agents

Trigger outbound calls from new leads, list and update lead records, send SMS, manage agents and teams, and subscribe to call lifecycle webhooks via Callingly.

Quickstart

Get started with Callingly 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:
"trigger a sales call to a new lead"

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

Capabilities

What an agent can do with Callingly API API.

Trigger an outbound sales call the moment a new lead is captured by posting to /calls

Route incoming leads to the right team or agent based on routing rules and availability

Send SMS follow-ups to prospects who do not answer the initial call

List and filter calls by status, agent, or team to feed dashboards and reporting

GET STARTED

Start building with Callingly API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Callingly API, keeping it validated and agent-ready. Callingly is a lead response automation platform that instantly calls sales reps the moment a new lead arrives so prospects are reached while interest is high. The API exposes call orchestration, lead routing, agent and team management, SMS messaging, multi-tenant client setup for agencies, and webhook subscriptions. It is suited to ops teams wiring Callingly into CRMs, ad platforms, and form tools without rebuilding the dialer logic.

Use Cases

Patterns agents use Callingly API API for, with concrete tasks.

★ Speed-to-Lead Auto Dialing

When a marketing form or ad platform produces a new lead, Callingly can be triggered immediately to call available sales reps and connect them to the prospect, typically within seconds. The API accepts the lead payload, picks an agent based on routing rules, and places the call without requiring a CRM integration. This compresses follow-up time from hours to seconds and lifts contact rates substantially.

POST /calls with the new lead payload, then poll GET /calls/{call_id} until status is connected or completed.

SMS Follow-Up After Missed Calls

If a sales rep cannot reach a prospect on the first attempt, the Callingly API can send a templated SMS through /sms to keep the conversation alive. This is useful for agencies running outbound campaigns where text follow-up converts a missed call into a scheduled callback. The same API surfaces status events via webhooks so the agent can sequence retries.

POST /sms with the lead phone number and a templated follow-up message after a missed call event.

Multi-Client Agency Management

Marketing agencies running Callingly across many clients can use the /clients endpoints to provision, activate, and deactivate accounts programmatically. This supports onboarding flows where a new client signs up in a portal and Callingly is set up automatically. The same endpoints let an agency pause or resume calling on a per-client basis when budgets change.

POST /clients to create a new agency client, then call POST /clients/{id}/active to activate calling for that client.

AI Agent Sales Outreach Orchestration

An AI agent monitoring inbound lead webhooks from forms or ads can call Callingly through Jentic to fire calls, send SMS, and reassign leads as priorities change. The agent stays out of the dialer logic itself and uses Callingly for orchestration, while Jentic handles credential isolation and operation discovery. This pattern keeps the agent focused on routing and content decisions rather than telephony plumbing.

Search Jentic for 'trigger a sales call', load the Callingly POST /calls schema, and execute it with the lead payload.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/calls

Trigger an outbound call to a lead

GET

/calls

List calls with filters

GET

/calls/{call_id}

Get a call by ID

GET

/leads

List leads with filters

PUT

/leads/{id}

Update a lead

POST

/sms

Send an SMS to a lead

POST

/clients/{id}/active

Activate or deactivate a client

POST

/calls

Trigger an outbound call to a lead

GET

/calls

List calls with filters

GET

/calls/{call_id}

Get a call by ID

GET

/leads

List leads with filters

PUT

/leads/{id}

Update a lead

POST

/sms

Why though Jentic?

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

Credential isolation

Callingly bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped access at execution time and never see the raw token in their context.

Intent-based discovery

Agents search by intent (e.g., 'trigger a sales call') and Jentic returns the matching Callingly operation with its input schema, so the agent can call /calls without browsing docs.

Time to first call

Direct Callingly integration: 1-3 days for auth, webhook handling, and lead payload mapping. Through Jentic: under 1 hour to search, load the schema, and execute the first call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio API

Lower-level voice and SMS primitives without lead-routing logic

Choose Twilio when the agent needs to build custom call flows or IVR; choose Callingly when speed-to-lead routing is the goal.

Alternative

Aircall API

Cloud phone system with team inboxes and call recording

Pick Aircall for inbound support and team telephony; pick Callingly for outbound speed-to-lead dialing.

Complementary

HubSpot Contacts API

Source of leads that Callingly can dial

Pull a new contact from HubSpot, then trigger Callingly to call the rep so the lead is reached within seconds.

FAQs

Specific to using Callingly API API through Jentic.

Why is there no official OpenAPI spec for Callingly API?

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

Callingly uses HTTP bearer token authentication. Each request must include an Authorization header with a bearer token issued from the Callingly dashboard. When called through Jentic, the bearer token is held in the Jentic vault and never exposed to the agent context.

Can I trigger a call to a new lead with the Callingly API?

Yes. POST to /calls with the lead payload (phone, name, source) and Callingly routes the call to an available agent on the configured team. The response includes a call_id that you can poll via GET /calls/{call_id} for status updates.

What are the rate limits for the Callingly API?

Callingly does not document a public rate limit table. In practice, lead-triggered call creation is the highest-volume endpoint and should be paced to match agent capacity. Contact Callingly support for account-specific limits before bulk backfills.

How do I send an SMS through Callingly via Jentic?

Search Jentic for 'send an sms via callingly', load the schema for POST /sms, and execute with the recipient phone number and message body. Jentic injects the bearer token at execution time.

Can the Callingly API manage multiple agency clients?

Yes. The /clients endpoints let you list, create, activate, deactivate, and delete client accounts. POST /clients/{id}/active toggles calling on or off for a specific client without removing their data.