Guide
Authentication and keys
Account keys, your personal key, and how to send them.
Account keys
Every operation except one works on a single account and takes an account key, created under Settings, then API. A key looks like <page id>:<secret>: the number before the colon is the account's id, so the key alone says which account it is for.
Send it in the Authorization header: Bearer 1000001:YOUR_SECRET. We store only a hash of the key and its last four characters, so a lost key can't be shown again; make a new one and revoke the old.
The same key also works on our own app endpoints, with a manager's permissions in the account. A key can't make other keys.
Your personal key
The profile operation (generateSingleUseLink) works on templates you own across accounts, and takes your personal key from your profile's API Settings. It looks like profile:<secret>.
Keeping keys safe
- Keep keys on your server; never put one in a web page or an app people download.
- Use one key per tool, named after it, so you can revoke one without breaking the rest.