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

# Introduction

> Yotel is an AI-native, browser-based call-centre dialer for Indian BPOs. The Yotel API lets you push leads, manage campaigns, receive call events, and build custom workflows from your own backend.

<Note>
  **Brand context** — Yotel is the product. Zetta AI is the company + the
  intelligence layer. You'll see both in responses (e.g. `X-Powered-By:
      Zetta AI`). For integration purposes they're the same platform.
</Note>

## What you can do with the API

Every integration we ship supports one of four customer archetypes:

<CardGroup cols={2}>
  <Card title="CRM push" icon="arrow-right-to-line">
    A nightly job in your CRM pushes new leads into a Yotel campaign.
    See [Quickstart](/quickstart).
  </Card>

  <Card title="Call outcomes → warehouse" icon="database">
    Subscribe webhooks to `call.ended`, stream rows into Snowflake / BQ / S3.
    See [Event catalog](/webhooks/event-catalog).
  </Card>

  <Card title="Embedded dialer" icon="phone">
    Build a softphone inside your own product using our WebRTC + auth primitives.
    (WebSocket API, v1.1 — coming soon.)
  </Card>

  <Card title="Agent analytics" icon="chart-line">
    Pull per-agent stats into your own BI. Read-only on existing agents + calls.
  </Card>
</CardGroup>

## What you need to know first

**Regional:** The Yotel API is hosted in GCP Mumbai (`asia-south1`). Low
latency from India; everywhere else expect \~150-300ms per call. Plan
your retry + timeout budgets accordingly.

**Versioning:** All public routes live under `/api/v1/`. We follow
semver for breaking changes; `v1` stays live for 12 months after a
`v2` launch is announced.

**Compliance:** Outbound dialing is TRAI-governed. Your leads MUST
be DND-scrubbed before we dial them — the dialer enforces this. The
[abandon rate cap](/concepts/errors#abandon-rate-exceeded) is
hardcoded at 3% (regulatory) with a 2.5% default target.

**Key format:**

```
yt_live_<32-hex>    production keys — can dial real calls
yt_test_<32-hex>    sandbox keys — calls are simulated (DB row written, no ESL originate)
```

Switch environments by switching keys. Same API surface, same base URL.

## Where to next

<CardGroup cols={3}>
  <Card title="5-minute quickstart" icon="rocket" href="/quickstart">
    Issue a key, push a lead, start a campaign.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    Headers, scopes, rate limits.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/webhooks/overview">
    Subscribe to real-time call + campaign events.
  </Card>
</CardGroup>