Skip to main content
The Get2Dial API reaches almost everything the product’s own UI does: users, telephony, campaigns, leads, dispositions, queues, CDRs, and recordings — plus webhooks for reacting to call and campaign events in real time.

​
How it works

The API is REST over HTTPS, versioned in the URL, base path /api/v1 at https://api.get2dial.com. Every request is authenticated the same way — a bearer token in the Authorization header — whether that token is your own session or a workspace API key. Responses are JSON, list endpoints are paginated with offset and limit, and errors follow one consistent shape across every endpoint. See Conventions and Errors.

​
When to use it

Reach for the API when you’re syncing data with a CRM or warehouse, provisioning users or telephony objects programmatically, or reacting to calls in real time via webhooks instead of polling.

​
What it affects

An API key only reaches what its granted capabilities cover — the same capability model that governs users. See Roles and permissions.

​
Limits and constraints

See Rate limits and Limits and quotas.

​
Next steps

Authenticate

Make your first request

Sync CDRs to your warehouse

Production checklist