GAIL (Lula API)

Name: GAIL (Lula API) API
Brand: GAIL (Lula API)
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsVoice TelephonyapiKey103 EndpointsREST

For Agents

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.

Connect the GAIL (Lula API) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GAIL (Lula 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.

Install Jentic One Beta (Self-Hosted)

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

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 GAIL (Lula API) API.

Place single and bulk outbound AI voice calls and download call recordings as audio or pre-signed URL

Create and run campaigns over contact lists with sequences, scripts, redialing rules, and detailed touchpoint reporting

Manage contact lists, individual contacts, and a do-not-call list to keep outreach compliant

Pull full conversation transcripts and run data extraction over completed conversations

GET STARTED

Start building with GAIL (Lula API) API

Explore with Jentic

View OpenAPI Document

Use for: I need to launch a multi-step calling sequence against my Q3 lead list, Create a script that handles renewal objections and attach it to a campaign, Pull the full transcript for a completed conversation, Add a phone number to the do-not-call list before our next campaign

Not supported: Does not handle PSTN number provisioning, billing, or hosted IVR design — use for AI calling, campaigns, sequences, scripts, conversations, SMS, DNC, and webhook configuration on the GAIL platform only.

Jentic publishes the only available OpenAPI document for GAIL (Lula API), keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for GAIL (Lula API), keeping it validated and agent-ready. GAIL (Lula API) — also called Galactus External — is the full Lula AI calling platform surface, with 103 endpoints covering calls, campaigns, contacts, contact lists, conversations, sequences, scripts, sessions, SMS, audio files, redialing rules, do-not-call lists, data extraction, organisations, use cases, webhooks, and a Zapier integration namespace. Authentication is by X-API-Key header generated in the Gail Portal under General > Integrations > API Keys.

Use Cases

Patterns agents use GAIL (Lula API) API for, with concrete tasks.

★ Multi-touch AI outreach with sequences and SMS

Sales teams orchestrate multi-touch outreach where each contact receives a calling sequence interleaved with SMS follow-ups. The Sequences and Scripts endpoints define the cadence and conversational logic, Campaigns drive the sequence over a contact list, and the Sms namespace handles message dispatch. The /v1/campaigns/{id}/describe endpoint previews exactly what will happen before the campaign goes live.

Create a 3-step sequence (call, SMS, call), attach it to a campaign over the renewal contact list, and call /v1/campaigns/{id}/describe to confirm the planned flow before starting.

Conversation analytics and data extraction

Operations teams run structured data extraction over completed conversations to pull buying intent, objections raised, and next-step commitments. The Conversations and DataExtraction tag groups expose endpoints to fetch transcripts and run extractions, which downstream BI tools or CRMs can ingest. This replaces manual review of recordings with an LLM-driven structured output.

List yesterday's completed conversations and run a data extraction job that returns intent and outcome fields per conversation.

Compliance: do-not-call and redialing rules

Compliance teams use the DoNotCall, RedialingRules, and Org endpoints to enforce outbound calling rules — adding numbers to the DNC list, configuring how often a number can be retried after no-answer, and inspecting org-level settings. Combined with the Webhook namespace, this supports an audit trail and real-time alerting on compliance events.

Add a list of phone numbers to the do-not-call registry and configure a redialing rule that limits retries to 2 attempts per 7 days.

Agent-driven full-platform GAIL automation via Jentic

An autonomous agent overseeing a sales motion needs to read the day's conversation outcomes, append fresh leads to a campaign, send SMS follow-ups, and notify the CRM via webhook — all without holding the GAIL API key. Jentic exposes every GAIL operation by intent and stores the X-API-Key in MAXsystem so the agent can chain operations safely across all 103 endpoints.

Search Jentic for 'gail run sequence', chain create-sequence, attach-to-campaign, start-campaign, and configure-webhook operations against the renewal use case.

Key Endpoints

103 endpoints — jentic publishes the only available openapi specification for gail (lula api), keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/calls

Start a single outbound call

POST

/v1/calls/bulk

Start outbound calls in bulk

POST

/v1/campaigns

Create a new campaign

GET

/v1/campaigns/{id}/describe

Describe what will happen when a campaign runs

GET

/v1/campaigns/{id}/touchpoints

Touchpoints history for a campaign

GET

/v1/calls/{callId}/recording-url

Pre-signed URL for a call recording

GET

/v1/audio_files

Catalog of available audio assets

POST

/v1/calls

Start a single outbound call

POST

/v1/calls/bulk

Start outbound calls in bulk

POST

/v1/campaigns

Create a new campaign

GET

/v1/campaigns/{id}/describe

Describe what will happen when a campaign runs

GET

/v1/campaigns/{id}/touchpoints

Touchpoints history for a campaign

Why though Jentic?

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

Credential isolation

The GAIL X-API-Key is stored encrypted in the Jentic MAXsystem vault. Jentic injects it as the X-API-Key header on every call to api.lula.com, keeping the raw key out of the agent's context and logs.

Intent-based discovery

Agents search by intent such as 'create gail sequence', 'extract data from conversation', or 'add to do not call list', and Jentic returns the matching GAIL operation with its parameter schema for direct execution.

Time to first call

Direct GAIL (Lula API) integration: 5-10 days to model 103 endpoints, sequence orchestration, webhook delivery, and DNC handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

GAIL API

The slimmer 15-endpoint v1 GAIL surface focused on calls, campaigns, contacts, and recordings

Use the lighter GAIL API when you only need calls, campaigns, and recording retrieval; use this fuller spec when you need sequences, scripts, conversations, SMS, or webhooks.

Alternative

Bland.ai

Competing AI voice agent platform with programmable conversational pathways

Choose Bland.ai when conversational pathways and inbound voice are central; choose GAIL (Lula API) for campaign-led outbound with sequences, SMS, and DNC management.

Alternative

Retell AI

Real-time low-latency AI voice agent platform

Pick Retell AI for ultra-low-latency real-time voice; pick GAIL (Lula API) for campaign orchestration with structured data extraction and reporting.

FAQs

Specific to using GAIL (Lula API) API through Jentic.

Why is there no official OpenAPI spec for GAIL (Lula API)?

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

GAIL (Lula API) uses an X-API-Key header. Generate the key in the Gail Portal under General > Integrations > API Keys and pass it as X-API-Key on every request to api.lula.com. Through Jentic, the key is held encrypted in MAXsystem and injected per request.

Can I extract structured data from completed conversations?

Yes. The DataExtraction tag group exposes endpoints for running structured extraction over completed Conversations, and you can fetch transcripts directly via the Conversations endpoints. This lets you pull intent labels, objections, and outcomes into a CRM without re-listening to call audio.

What are the rate limits for the GAIL (Lula API)?

Specific rate limits are not declared in the spec. Expect per-account quotas tied to the Lula plan and outbound carrier capacity. Design clients to back off on 429 responses and prefer the bulk and campaign endpoints over tight loops on /v1/calls.

How do I describe a campaign before starting it through Jentic?

Search Jentic for 'describe gail campaign', load GET /v1/campaigns/{id}/describe, and execute it with the campaign ID. The response details how contacts are sourced and converted to assignments, what sequences will run, and what scripts will execute at each step — useful as a dry-run before you call POST /v1/campaigns/{id}/start.

Does GAIL (Lula API) support SMS as well as voice?

Yes. The Sms tag group exposes SMS dispatch and handling endpoints, and SMS steps can be combined with voice steps inside Sequences. This is what lets you build call-then-SMS multi-touch outreach in a single campaign.