Skip to main content
The Click-to-Call API lets your application trigger an outbound phone call without anyone touching the TalkChief dashboard. You send a single authenticated POST request with a destination number and a caller ID, and TalkChief connects the call through your communications infrastructure — routing it to the right agent or queue and attaching any metadata you want to carry through to the call detail record. This makes it straightforward to add a “Call me” button to your website, a one-click dial button to your CRM, or an automated outreach trigger to your sales workflow.
Your exact API base URL and the list of available from numbers for your account are in your TalkChief dashboard under Settings → Developers. The call itself is always human-operated — Click-to-Call initiates the connection; an agent handles the conversation.

Use Cases

CRM Click-to-Dial

Render a “Call” button next to every contact record. One click sends a POST request and the agent’s phone rings, with the customer on the line before the agent even picks up.

Website Callback Request

Let visitors enter their number and request an immediate callback. Your backend receives the form submission and fires a Click-to-Call request in real time.

Sales Workflow Trigger

Kick off a call automatically when a lead reaches a specific stage in your pipeline — no manual dialing, no context switching.

Power Dialer Integration

Connect Click-to-Call to your internal dialer queue to move through a list of contacts programmatically while keeping a human agent in every conversation.

Endpoint

Initiate a call by sending a POST request to the calls endpoint on your customer-specific base URL.

Request Parameters

string
required
The destination phone number to dial, in E.164 format (e.g., +12025551234). Numbers not in E.164 format will be rejected with a 400 error and an INVALID_NUMBER code.
string
required
The TalkChief number to present as the outbound caller ID, also in E.164 format. This must be a number provisioned on your account. Your available numbers are listed in Settings → Phone Numbers in the dashboard.
string
Route the call directly to a specific agent by their TalkChief user ID. If omitted and queue_id is also omitted, the call follows your account’s default routing rules.
string
Route the call through a specific call queue. The first available agent in the queue answers the call. Cannot be used together with agent_id — provide one or the other.
object
A flat key-value object of arbitrary strings attached to the call record. Use this to pass your internal identifiers — such as a CRM contact ID, deal ID, or campaign tag — so you can correlate the call detail record event back to your system when TalkChief delivers it via webhook.

Example Request

Response

A successful 201 Created response confirms that the call has been initiated in TalkChief’s infrastructure. It does not mean the call has been answered — only that it has been queued for delivery.
string
The unique identifier for this call, prefixed with c_. Store this to correlate with CDR webhook events and any future status lookups.
string
The initial status of the call. Will be "initiated" immediately after creation. Subsequent status changes are delivered via CDR webhook.
string
ISO 8601 timestamp indicating when the call was created in TalkChief’s system (e.g., "2024-11-15T14:32:00Z").
Example response body:

Tracking the Call

The 201 response tells you the call started — but to know what happened next (duration, disposition, recording URL, which agent answered), you need the completed call detail record. Configure a CDR webhook to receive a call.completed event the moment the call ends.
Pass your CRM contact ID (or any internal reference) in the metadata field when initiating the call. TalkChief echoes that same metadata object back in the CDR webhook payload, so you can match the completed-call record to the right contact or deal without storing a separate call_id mapping.
When the call completes, TalkChief POSTs a call.completed event to your webhook endpoint containing the full call record — including duration_seconds, recording_url, agent_id, and your original metadata. See the Webhooks reference for the full payload schema and signature verification instructions.