Dialpad API

Name: Dialpad API
Brand: Dialpad API
Availability: InStock

✓ Official Vendor SpecCommunicationsVoice Telephonybearer25 EndpointsREST

For Agents

Place calls, send SMS, manage contacts and users, and configure access control across Dialpad's cloud telephony platform.

Install Jentic One Beta

Connect the Dialpad API to your agent

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

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 Dialpad API.

Place outbound calls and look up call details and recordings

Send and receive SMS messages from Dialpad numbers

Manage contact records, including create, update, and search

Provision users and assign offices, call centres, and policies

GET STARTED

Start building with Dialpad API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Dialpad API for, with concrete tasks.

★ CRM Click-to-Call Integration

Add click-to-call to a CRM record so reps dial directly from the contact view. The Dialpad calls endpoint accepts a from-user and a destination number, and Dialpad places the call on the rep's device. The integration also pulls call history and recordings back to the CRM record after the call ends.

When a rep clicks call on a contact record, POST to /calls with the rep's user id and the contact's phone number, then post the resulting call id back to the CRM

SMS Customer Outreach

Send transactional and conversational SMS from Dialpad numbers — appointment reminders, support follow-ups, or two-way conversations. POST /sms takes a from-number, to-number, and body, and Dialpad delivers the message and reports its status. Inbound SMS can be received via webhook for two-way flows.

Send an SMS from the support number to +14155551212 with a templated reminder body, then track delivery via the returned message id

Call Centre Workforce Management

Manage a Dialpad call-centre workforce — provisioning users, assigning them to call centres, applying access control policies, and pulling call activity for reporting. The users, callcenters, and accesscontrolpolicies endpoints together form a small workforce-management surface for ops teams.

Provision new agent user agent42, assign them to call centre cc-eu-tier1, and apply the standard agent access control policy

AI Agent Telephony Connector

Give an AI agent a callable telephony layer through Jentic. The orchestrator searches for "send an SMS" or "place a call" and Jentic returns the matching Dialpad operation with its schema, so the agent can dial out or message a customer without integrating the Dialpad SDK directly.

When a support ticket needs a callback, place a Dialpad call from the on-call user to the customer's number and append the call id to the ticket timeline

Key Endpoints

25 endpoints — the dialpad api exposes dialpad's cloud telephony and contact-centre platform — calls, sms, contacts, users, offices, call centres, access control policies, and webhooks.

METHOD

PATH

DESCRIPTION

POST

/calls

Place an outbound call

GET

/calls/{call_id}

Retrieve call details and recording references

POST

/sms

Send an SMS from a Dialpad number

GET

/contacts

List or search contacts

GET

/users/{user_id}

Retrieve a user record

POST

/accesscontrolpolicies/{id}/assign

Assign an access control policy to a user

POST

/calls

Place an outbound call

GET

/calls/{call_id}

Retrieve call details and recording references

POST

/sms

Send an SMS from a Dialpad number

GET

/contacts

List or search contacts

GET

/users/{user_id}

Retrieve a user record

POST

Why Jentic?

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

Credential isolation

Dialpad bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped execution token — the raw Dialpad token never enters the model context.

Intent-based discovery

Agents express intent ("place a call", "send an SMS", "assign a policy") and Jentic returns the matching Dialpad operation with its input schema.

Time to first call

Direct Dialpad integration: 1-2 days for auth, call lifecycle, and webhook handling. Through Jentic: under 1 hour for the common call and SMS paths.

FAQs

Specific to using Dialpad API through Jentic.

What authentication does the Dialpad API use?

Dialpad uses HTTP Bearer authentication. The token is generated in the Dialpad admin console and scoped to an account. Through Jentic the token is stored in the encrypted vault and never enters the agent's context.

Can I send SMS from a Dialpad number with one call?

Yes. POST /sms with a from-number, to-number, and body sends the message and returns its id. Delivery status is reported via the message resource and via webhook subscriptions if registered.

What are the rate limits for the Dialpad API?

Dialpad applies per-account rate limits roughly in the low hundreds of requests per minute. The exact limit appears in 429 response headers; retry with exponential backoff is recommended for bulk imports.

How do I place a call through Jentic?

Run a Jentic search for "place a Dialpad call". Jentic returns POST /calls with its input schema (user id, target number). Load the schema, populate the fields, and execute — no need to read the Dialpad OpenAPI spec.

Does the API expose call recordings?

Yes. GET /calls/{call_id} returns metadata including recording references when recording is enabled for the user or call centre. Recordings themselves are fetched from the URLs included in that response.

How do I install the Jentic SDK to call Dialpad?

Run pip install jentic, set JENTIC_AGENT_API_KEY to your ak_* key, then use Jentic with SearchRequest, LoadRequest, and ExecutionRequest. Sign up at https://app.jentic.com/sign-up.

Dialpad API

Connect the Dialpad API to your agent

Capabilities

Start building with Dialpad API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs