Vibrato Call API

Name: Vibrato Call API
Brand: Vibrato Call API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsVoice Telephonybearer23 EndpointsREST

For Agents

Place AI-driven phone calls, run call campaigns, manage contacts, and configure task templates through Vibrato across 23 endpoints with bearer-token authentication.

Connect the Vibrato Call API to your agent

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

Place an outbound AI-driven phone call to a specific contact

Build call campaigns that target a contact list with a shared task template

Manage contacts with name, phone number, and metadata fields

Define reusable task templates that describe what the AI should accomplish on the call

GET STARTED

Start building with Vibrato Call API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Vibrato Call API, keeping it validated and agent-ready. The Vibrato Call API powers AI-driven outbound and inbound phone calls. Across 23 endpoints it covers calls, campaigns, contacts, and task templates — the building blocks for automating phone outreach with AI voice. Authentication is HTTP bearer, and the API exposes a clean CRUD pattern across each resource so an integration can list contacts, build a campaign, and launch calls programmatically.

Use Cases

Patterns agents use Vibrato Call API for, with concrete tasks.

★ Automated Lead Follow-Up Calling

Sales teams configure a campaign that calls every new inbound lead within minutes, using a task template that qualifies the lead and books a meeting if appropriate. Vibrato handles the AI voice, the contact iteration, and the per-call status tracking, so the sales-ops integration only needs to push contacts and read call outcomes.

Create a campaign 'New-Lead-Followup' that calls all contacts created in the last hour using task template id 42.

Single AI Call from a Workflow Trigger

When a workflow tool detects a high-value event (a payment failure, a demo no-show), it can place a single targeted AI call rather than running a full campaign. POST /calls accepts a contact id and task template and returns the call uuid. The integration then polls GET /calls/{id} for status until the call completes.

Place a single call to contact uuid 'cnt_99' using task template 'payment-failure-recovery' and poll GET /calls/{id} until status is final.

Contact List Synchronisation

CRM-driven contact lists feed Vibrato's contacts resource so campaigns target the latest customer record set. POST /contacts adds a contact, GET /contacts lists them with filters, and PATCH /contacts/{id} updates phone or metadata. This keeps the AI calling layer aligned with the CRM source of truth.

List the firm's CRM contacts and POST any missing ones to /contacts in Vibrato.

AI Agent Voice Outreach

An AI agent assigned to a customer-success workflow can place calls, queue campaigns, and update task templates without UI navigation. Through Jentic the agent finds each operation by intent ('place an AI call' or 'create a call campaign') and Vibrato bearer tokens stay in the encrypted vault rather than reaching the agent context.

Create a campaign targeting contacts tagged 'renewal-30d' using template 'renewal-call' and start it.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/calls

Place an AI-driven outbound call

GET

/calls/{id}

Retrieve a single call's status and details

POST

/campaigns

Create a call campaign

GET

/campaigns

List campaigns

PATCH

/campaigns/{uuid}

Update a campaign

POST

/contacts

Create a contact

GET

/contacts

List contacts

POST

/calls

Place an AI-driven outbound call

GET

/calls/{id}

Retrieve a single call's status and details

POST

/campaigns

Create a call campaign

GET

/campaigns

List campaigns

PATCH

/campaigns/{uuid}

Update a campaign

POST

Why Jentic?

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

Credential isolation

Vibrato bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped invocation capability — the raw token never enters the agent's context, which matters because the token authorises real outbound calls that incur cost.

Intent-based discovery

Agents search by intent (e.g. 'place an AI call' or 'create a call campaign') and Jentic returns the matching Vibrato operation with its full input schema for direct execution.

Time to first call

Direct Vibrato integration including auth, contact sync, campaign config, and call-status polling: 2-3 days. Through Jentic: under 1 hour — search, load, execute.

FAQs

Specific to using Vibrato Call API through Jentic.

Why is there no official OpenAPI spec for Vibrato Call API?

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

Vibrato uses HTTP bearer authentication — the bearer token is sent in the Authorization header. Through Jentic this token is stored encrypted in the vault and the agent receives only a scoped invocation capability, so the raw token never enters its context.

Can I place a single AI phone call with the Vibrato API?

Yes. POST /calls accepts a contact reference and the task-template id and returns the call's uuid. Poll GET /calls/{id} for the latest status, recording references, and outcome details.

What are the rate limits for the Vibrato Call API?

The spec does not declare explicit rate limits. Vibrato meters concurrent calls and total minutes by plan; production integrations should respect 429 responses with backoff and avoid spinning up many campaigns simultaneously without checking quota first.

How do I create a call campaign through Jentic?

Search Jentic for 'create a vibrato call campaign'. Jentic returns POST /campaigns with its input schema; load it with the contact filter and task-template id, execute, and capture the returned campaign uuid for follow-up calls.

Can I update a contact's phone number via the API?

Yes. PATCH /contacts/{id} accepts the partial update payload — for example a new phone number or metadata — and returns the updated contact record. POST /contacts is used for new records; PATCH is used to keep the list aligned with upstream CRM changes.

Vibrato Call API

Connect the Vibrato Call API to your agent

Capabilities

Start building with Vibrato Call API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs