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.What you can do with the API
Every integration we ship supports one of four customer archetypes:CRM push
A nightly job in your CRM pushes new leads into a Yotel campaign.
See Quickstart.
Call outcomes → warehouse
Subscribe webhooks to
call.ended, stream rows into Snowflake / BQ / S3.
See Event catalog.Embedded dialer
Build a softphone inside your own product using our WebRTC + auth primitives.
(WebSocket API, v1.1 — coming soon.)
Agent analytics
Pull per-agent stats into your own BI. Read-only on existing agents + calls.
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 is
hardcoded at 3% (regulatory) with a 2.5% default target.
Key format:
Where to next
5-minute quickstart
Issue a key, push a lead, start a campaign.
Authentication
Headers, scopes, rate limits.
Webhooks
Subscribe to real-time call + campaign events.