canonical: https://jentic.com/apis/lula.com

# Lula GAIL APIs

Lula's GAIL is an AI-powered voice calling platform for outbound sales, renewals, and collections outreach. Its APIs place single and bulk AI voice calls, run campaigns over contact lists, and retrieve call recordings and CSV reports. The fuller platform surface adds multi-step sequences, conversational scripts, SMS, conversation transcripts, structured data extraction, do-not-call lists, redialing rules, and webhooks. Authentication is by an X-API-Key header generated in the Gail Portal.

## For AI agents

An agent can place single or bulk AI voice calls, build and run calling campaigns over contact lists, and pull recordings and CSV reports, then extend into multi-step sequences, scripts, SMS follow-ups, conversation transcripts, data extraction, do-not-call enforcement, and webhook events across Lula's GAIL platform.

## Scope

Use for: Outbound AI voice calling on Lula GAIL: single and bulk calls, campaigns over contact lists, sequences, scripts, SMS, conversation transcripts, data extraction, do-not-call and redialing compliance, recordings, CSV reports, and webhooks

Not supported:
- PSTN number provisioning
- billing management
- inbound IVR routing
- hosted IVR design

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| GAIL (Lula API) | communications | 103 | Run the full Lula AI calling platform: calls, campaigns, contact lists, conversations, sequences, scripts, SMS, do-not-call lists, sessions, and webhooks across 103 endpoints. |
| GAIL API | communications | 15 | Launch outbound AI voice calls one-off or in bulk, run campaigns over a contact list, and retrieve call recordings and CSV reports through Lula's GAIL platform. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Place outbound calls, run campaigns, and pull recordings or CSV reports | gail | The slim 15-endpoint surface covers the core call and campaign lifecycle without the extra platform tags. |
| Run multi-step sequences, scripts, SMS, conversation transcripts, data extraction, do-not-call lists, or webhooks | gail-api | The fuller 103-endpoint spec exposes the whole GAIL platform beyond basic calls and campaigns. |

## Cross-API use cases

### Start on the slim call API, grow into full sequences

A team begins with the 15-endpoint gail surface to create a campaign, bulk-add a contact list, start it, and pull the CSV report. When they need multi-step cadences, the fuller gail-api adds sequences, scripts, and SMS steps so the same campaign becomes a call-then-SMS multi-touch flow with a describe preview before it runs.

Example prompt: Create and start a renewal campaign with the gail API, then use gail-api to attach a 3-step call-SMS-call sequence and describe the planned flow before the next run.

### Call recordings plus conversation analytics for QA

Reviewers retrieve pre-signed recording URLs from the gail API for completed calls, then use the gail-api conversation and data-extraction endpoints to pull transcripts and structured intent and outcome fields, mapping each recording back to what was said and decided.

Example prompt: Fetch a recording URL for a callId via the gail API and run a data-extraction job over the matching conversation with gail-api to return intent and outcome labels.

### Compliant outbound calling with DNC and reporting

Before a campaign runs, an agent adds numbers to the do-not-call list and sets redialing rules through the gail-api compliance endpoints, then launches and reports on the campaign through the gail surface, keeping outreach within retry and DNC constraints.

Example prompt: Add a number list to the do-not-call registry and set a retry limit with gail-api, then start the campaign and pull its CSV report through the gail API.

## Why Jentic

- **Setup:** Wiring GAIL by hand means sending the X-API-Key header on every request and threading one key across calls, campaigns, sequences, SMS, conversations, and webhooks on two specs. With Jentic you install Jentic One once, add the GAIL APIs from the Jentic directory, store the key once, and your agent calls either surface.
- **Permission scoping:** GAIL puts the campaign id in the URL path, so your own rules in Jentic One can pin the agent to one campaign and a chosen set of operations. You decide whether it may place calls, add contacts to the do-not-call list, or start campaigns, and anything you do not grant stays off limits across both APIs.
- **Credential handling:** Your GAIL X-API-Key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, and the same stored key covers both the slim and full specs.
- **Discovery method:** Agents search the Jentic directory by intent such as start an outbound call, run a calling sequence, or add a number to the do-not-call list, and Jentic returns the matching GAIL operation with its parameter schema so the agent calls the right endpoint on the right spec.

## Related vendors

- **Bland.ai** — AI voice agent platform with programmable conversational pathways for outbound and inbound calls.
- **Retell AI** — Real-time low-latency AI voice agent platform for conversational calling.
- **Twilio** — Programmable voice and SMS infrastructure that underpins outbound calling and messaging workflows.
- **Vapi** — Voice AI platform for building and running phone-based agents.

## FAQ

### What is Lula GAIL and what can an agent do across its APIs?

GAIL is Lula's AI voice calling platform. Across its APIs an agent can place single and bulk outbound calls, run campaigns over contact lists, and retrieve recordings and CSV reports, then extend into sequences, scripts, SMS follow-ups, conversation transcripts, data extraction, do-not-call enforcement, and webhook events.

### What is the difference between the two GAIL APIs?

The gail API is a slim 15-endpoint surface for the core call and campaign lifecycle: single and bulk calls, campaigns, contacts, and recordings. The gail-api spec is the fuller 103-endpoint platform that adds sequences, scripts, conversation transcripts, data extraction, SMS, do-not-call lists, redialing rules, sessions, and webhooks.

### Do both APIs share the same authentication?

Yes. Both use an X-API-Key header generated in the Gail Portal under General, Integrations, API Keys. A single Lula key works against either surface, so an agent does not need separate credentials to move between the slim and full specs.

### Which API should I choose to start?

Start with the gail API if you only need to place calls, run campaigns, and pull recordings or reports. Move to the gail-api spec when you need multi-step sequences, conversational scripts, SMS, conversation analytics, or compliance controls like do-not-call lists and redialing rules.

### How does GAIL support compliant outbound calling?

The gail-api spec exposes do-not-call list management and redialing rules so you can block numbers and cap retries before a campaign runs. Combined with webhook events, this gives you an audit trail and real-time alerting on outbound calling activity.

### Can I analyze conversations after calls complete?

Yes, through the gail-api spec. Its conversation endpoints return full transcripts and its data-extraction endpoints run structured extraction over completed conversations, letting you pull intent labels, objections, and outcomes into a CRM without re-listening to the audio.