Getting started

Authentication

One bearer token, one scope per endpoint — and read always separate from write.

Send the key as a bearer token on every call. Keys start with tak_ so they can be recognised if one ever ends up in a log or a commit.

HTTP

Authorization: Bearer tak_your_key_here

Scopes

Every endpoint requires one scope, and read and write are always separate — a key that looks up a phone number should not be able to overwrite the whole address book.

Recordings stand on their own. recordings:read is deliberately separate from
calls:read: a summary is your notes about a conversation, while the recording is the
conversation — the customer's voice, with everything she said along the way.

The conversation cannot be edited through the API. Transcript, summary and recording
are a record of what was said — and a record another system can rewrite is not one.
calls:write sets labels and marks a call handled, nothing else.

Lifetime

Scopes can be changed on an existing key, and a key can be revoked at any time — it stops working immediately. Keys never expire on their own.