Keys
How to get a key, what each access allows, and how to send it.
A member creates a key in the app, under Settings, API and MCP (the menu under your name, bottom left), with Create key: a name and an access.
| Access | May |
|---|---|
| Read | Read radars, signals, sweeps, companies, custom sources, filters and newsletters |
| Read and write | The same, and add, edit and delete companies, custom sources and radars; create, change and delete newsletters and their blocks, add and remove recipients, and approve or skip an issue |
A key starts with ak_. It is shown once, when it is created, and never again: copy it then.
The list shows its first characters, its access and when it was last used. Revoke stops it
at once.
A key belongs to the account, not to the person who made it: it keeps working when that person leaves the account. Revoke it then.
Sending it
Send the key on every request:
Authorization: Bearer <your key>A request without a key, with an unknown key or with a revoked key fails with 401 unauthorized. A read key that asks to write fails with 403 read_only_key. See
Errors.