Skip to main content
The Clearskies API is in beta and available on request. To turn it on for your workspace, email support@clearskies.cc.
Every request carries an API key in the Authorization header. A key reads your workspace’s Context Graph, so treat it like a password.

What a key can read

A key reads every account, contact, and deal in the workspace. Calls follow the same rule as in the Clearskies app: a key reads the calls of the person who created it, the calls shared with the workspace, and, if that person is an admin, every call. Other calls are left out of queries and counts, and their transcripts answer 404.

Create a key

  1. In Clearskies, go to Context Graph > API keys in the sidebar.
  2. Click Create key.
  3. Name the key after the thing that will use it, such as “Revenue dashboard”. You’ll pick it out of this list when you revoke it.
  4. Copy the key and store it somewhere safe, such as your secrets manager.
Clearskies shows the key once. It stores only a hash, so a lost key can’t be recovered; create a new one instead.

Send the key

Pass the key as a bearer token:

Revoke a key

On Context Graph > API keys, click Revoke key next to the key. Clearskies checks the key on every request, so its next call fails.

When a working key starts failing

A key belongs to the person who created it. It stops working when that person is deactivated or leaves the workspace, as well as when it’s revoked. The API answers each case with 401 UNAUTHORIZED, so check them all; see Errors and rate limits.