Reference · built on requestConnectorVoice & contact center

Dialpad

Call events, call center status, transcripts, and agent duty status from Dialpad, with calls and texts you approve.

About

Dialpad is a cloud phone system with call centers, sold by Dialpad. Its REST API is served from dialpad.com/api/v2 with a sandbox at sandbox.dialpad.com. Event subscriptions push call, SMS, contact, agent status, and change log events to a webhook or a WebSocket as JWTs signed with a secret you choose. A Company Admin creates the API key under Admin Settings > My Company > Authentication > API Keys.

Through Fibric, an operator reads call center status and call events, pulls the transcript when a call ends, and proposes a call, a duty status change, or a text. You approve it. The change is applied once and the record shows what happened and why.

This is a reference listing. It documents what Fibric would read from Dialpad and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Call events with states such as ringing, connected, hangup, recording, csat, and recap_summary, delivered per company, office, call center, or user
  • Call center status through GET /api/v2/callcenters/{id}/status: available and on-duty operators, queued calls, and the longest queued call in seconds
  • Call transcripts through GET /api/v2/transcripts/{call_id}, returned as lines with speaker, time, and type
  • Agent status events carrying on_duty_status values available, unavailable, occupied, wrapup, or busy, subscribed at company level
  • SMS events for inbound and outbound messages; text content only with the message_content_export scope
  • Stats exports through POST /api/v2/stats for calls, csat, dispositions, onduty, recordings, texts, and voicemails by user, office, department, or call center

Proposed actions

  • Target capability: propose an outbound call for a user through POST /api/v2/call, which rings the user's devices first
  • Target capability: propose an operator's duty status change through PATCH /api/v2/callcenters/operators/{id}/dutystatus with a reason
  • Target capability: propose a text message through the SMS API, which Dialpad limits to 100 sends per minute
  • Target capability: propose a webhook and a call event subscription through POST /api/v2/webhooks and POST /api/v2/subscriptions/call

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Summarize the call as it ends

    A call event in the recap_summary or call_transcription state carries the summary and transcript. The operator reads it and proposes a note for the record you pick.

    With Call Summary

  • Act on a queue backing up

    The operator polls call center status for queued calls and the longest wait. Past your threshold, it proposes duty status changes for a supervisor to approve.

    With Breach Watch, Intraday Balance

  • Call back a low CSAT score

    When a csat event reports a low score, the operator drafts a return call through POST /api/v2/call and holds it until a lead approves.

    With Detractor Callback

  • Report on dispositions weekly

    A stats export by call center returns dispositions and csat for the period. The operator proposes the week's read with the export id as evidence.

    With Contact Drivers

Requirements

  • A Dialpad company with a Company Admin who can create API keys under Admin Settings > My Company > Authentication > API Keys
  • The recordings_export scope on the key if call events should include recording URLs
  • The message_content_export or message_content_export:all scope to read SMS text; without it, content is excluded
  • A public HTTPS endpoint for webhooks, or a WebSocket client that refreshes its connection token every hour
Authentication
An API key created by a Company Admin, sent as a bearer token in the Authorization header, or an OAuth 2.0 authorization code flow with scopes such as recordings_export and calls:list.

Limits

  • Rate limit is 20 requests per second per company; initiating calls is capped at 5 per minute per user target
  • Subscriptions are capped at 100 per type across all targets in a company, and 10 per type when targeting the company itself
  • Agent status events can only be subscribed at company level, not per call center
  • WebSocket connection tokens expire one hour after issue and the connection is closed after one hour

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Dialpad ↗

Questions and answers

How does Dialpad deliver events?
Through event subscriptions. You create a webhook with a hook_url and secret, then a subscription per event type: call, SMS, contact, agent status, or change log. Events arrive as JWTs signed with your secret. A WebSocket option delivers the same events without a public endpoint; its tokens expire after one hour.
Which rate limits apply?
Dialpad documents 20 requests per second per company. Endpoint limits also apply: create contacts 100 per minute, initiate calls 5 per minute per user target, send SMS 100 per minute. Transcript and call center status reads allow 1200 per minute. Dialpad reserves the right to change these.
Can the connector read a call recording?
Call events include recording details when the API key carries the recordings_export scope. Transcripts come from GET /api/v2/transcripts/{call_id}. Recording share links are a separate resource in the API reference.
Ask about Dialpad

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.