> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get2dial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Developers overview

> What the Get2Dial API covers, how authentication works, and where to start if you're integrating for the first time.

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](/developers/conventions) and
[Errors](/developers/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](/developers/webhooks/overview) 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](/account/roles-and-permissions).

## Limits and constraints

See [Rate limits](/developers/rate-limits) and [Limits and quotas](/reference/limits-and-quotas).

## Next steps

<CardGroup cols={2}>
  <Card title="Authenticate" href="/developers/authentication" />

  <Card title="Make your first request" href="/developers/make-your-first-request" />

  <Card title="Sync CDRs to your warehouse" href="/developers/recipes/sync-cdrs-to-your-warehouse" />

  <Card title="Production checklist" href="/developers/production-checklist" />
</CardGroup>