Skip to content

Talki Developers

Bring the calls, appointments and contacts Talki handles into your own software.

Run it without a key

This button makes a real request. The endpoint takes no credential and answers with one sample call in the same envelope GET /v1/calls returns: your integration sends a key, this one does not, because a credential does not belong in a browser.

GET https://api.talki.it/demo/call

Read what happened on a call

Every answered call produces a record: caller, billed duration, outcome and the agent’s summary. Pull it into your CRM as an activity.

Sync and write appointments

Change feeds and signed events keep calendars aligned. Check availability, then create, reschedule, or cancel bookings with idempotent writes.

Receive signed webhooks

Signed webhooks fire on call, appointment, contact and usage events. Delivery logs and manual redelivery help you recover when your endpoint is unavailable.

Build without a customer

Registering an app issues a sandbox: a Talki account of your own, already populated, that you can ask to have had a call and reset when you are done.

Offer Talki inside your software. Your customers can pay Talki themselves, or you can pay for them: they get Talki with no subscription of their own, you set your price, and you choose and change their plan through the API.

Building with an AI agent?

Paste this into your assistant. It points at machine-readable copies of these docs, so it works with the contract instead of guessing at it.

Use the Talki public API documentation:
- Index: https://developers.talki.it/llms.txt
- Full documentation: https://developers.talki.it/llms-full.txt
- OpenAPI contract: https://developers.talki.it/openapi.yaml
- Any single page as markdown: add .md to its path, e.g. https://developers.talki.it/webhooks.md

Context: the REST API is in private beta on the Business plan; webhooks are
available from Pro upward. Base URL https://api.talki.it/v1, authenticated with
a bearer API key. Dated contract 2026-10-01 (draft).

Rules: the OpenAPI document is authoritative — where it disagrees with prose,
follow the document. Do not invent field names, enum values or endpoints; if
something is not in the contract, it is not public yet.