Authentication

Every request needs an API key as a bearer token.

curl https://protoki.com/api/v1/meetings \
  -H "Authorization: Bearer pk_live_your_key"

A key belongs to exactly one workspace. Every query is narrowed to that workspace on the server, and for a personal key it is narrowed further to the meetings of that one person — by the same rule that applies in the app. The full key is shown only once, when you create it. Keep it safe.

Two kinds of key

Account key

Sees every meeting in the workspace. A workspace admin creates and revokes account keys under Admin → API keys.

Personal key

Sees only the meetings that the person also sees in the app: the ones they own, follow, or take part in by email address. Read-only.

Anyone creates their own under Settings, provided the admin has enabled personal keys for the workspace. The response formats are identical to an account key — only the set of meetings differs.

If the section is not there, the page says why. There are three conditions: you are signed in, the admin has enabled personal keys, and the package includes them.

Expiry

Every key has a lifetime. You choose it when creating the key: 30, 90 or 365 days — 90 by default — or unlimited.

Before a key expires, Protoki warns you by email 7 days and 1 day ahead, and in the app. After that the API answers 401.

An expired or revoked key cannot be reactivated. Create a new one and store it in the connected applications.