Overview

Talki answers a business’s phone, books appointments, and records who called and why. The developer platform lets another system—usually a CRM—react to that activity without using Talki’s private dashboard endpoints or a user’s login session.

Available now

Capability	Surface	Status
Validate an API key and identify its account	GET /v1/account	Private beta
Read call records and summaries	GET /v1/calls and GET /v1/calls/{call_id}	Private beta
Receive call, appointment, contact, and usage events	Signed webhooks	Available from Pro

See the generated API reference for the complete REST contract. If an operation is not in that reference, it is not a public endpoint.

Planned, not yet available

Read and narrowly scoped write endpoints for appointments, contacts, services, and availability are being designed for the same /v1 surface. OAuth will let multi-customer platforms install without copying API keys. Do not build against those operations until they appear in the reference and changelog.

What it deliberately does not expose

These are policy, not gaps waiting to be filled:

• Verbatim call transcripts and audio. Not available through the API, and not planned. Any future access would be a separate, separately-granted scope.
• Token counts and model costs. Internal accounting.
• Inbox state (read / archived flags) and refused-call rows. Dashboard concerns, not contract concerns.

Availability

The REST API is a Business plan feature. A request made with a valid credential on a lower plan fails with a distinct plan_upgrade_required error, so you can tell the customer to upgrade rather than showing them a permission error.

Webhooks are a separate capability and remain available from Pro upward.

Base URL

https://api.talki.it/v1

The API accepts and returns JSON over HTTPS. All paths in the reference are relative to https://api.talki.it; /v1 is already part of each path.