Skip to main content

Get started

Authentication

Every request carries an API key as a bearer token in the Authorization header. File download links are the one exception: the link is its own credential.

Request

curl https://api.clickr.cloud/v2/account \
  -H "Authorization: Bearer $CLICKR_API_KEY"

Create a key

In Clickr, open Settings and choose Create key under API keys. A key starts with clickr_sk_ and is shown once: Clickr keeps only a hash of it, so a lost key is replaced, not recovered.

Each person on an account has their own keys, and a key acts with its person's access. Narrow someone's access and every key they hold narrows at once; when they leave the account, their keys stop working.

Send it

Put the key in the Authorization header as Bearer clickr_sk_… on every request, over HTTPS. Keep it on a server: a key in a web page or a mobile app can be read by anyone who has it.

Rotate or revoke it

Rotating a key from Settings gives you a new one. Choose whether the old key stops at once or keeps working for 24 hours or 7 days, so you can move your integrations over without downtime. Settings shows when a rotated key was last used, so you can tell when nothing is still calling with it.

Assistants

Claude, ChatGPT and other assistants connect to the MCP server at https://api.clickr.cloud/mcp with OAuth instead: you sign in to Clickr when you add the connector, so there is no key to paste. MCP server

When a key is refused

The response is 401, with one of these errors.

StatusErrorWhen
401No API Key providedThe Authorization header is missing.
401No account found for api key providedThe key isn't recognised: mistyped, revoked, or held by someone who has left the account.
401No integration found for accountThe account has no connector connected yet.
401No account foundThe account behind the key no longer exists.