Skip to Content
APIAuthentication

API tokens

Personal API tokens are static secrets for scripts. Two independent rules govern them — who can create one and what an existing one can do.

Creating tokens (website only)

Tokens are created and managed on the dashboard API Tokens page with a signed-in browser session. The token API itself cannot create, list or revoke tokens.

  • Eligibility: creating a token requires an active paid plan; every paid tier qualifies. Trialing, canceled, past_due, absent or unknown plans do not.
  • Slots: at most three stored tokens per account. Expired but unrevoked tokens still occupy a slot until you revoke them.
  • Expiry: each token either never expires or has a finite expiry — the form offers “Never” and “30 days”, and the expiry is at most 365 days.
  • Secret: the plaintext key is shown exactly once, in the creation confirmation. Store it immediately; there is no way to view it again.
  • Revocation: revoke a token to free its slot and deny further use on its next request. Revocation is irreversible.

Listing and managing existing tokens (name, timestamps, active/expired/revoked status, last-used time, remaining slots) is always available on the dashboard page, whether or not the account currently has an active plan.

Using a token

Send the key with the Token authorization scheme:

Authorization: Token <key>

A malformed, unknown, revoked or expired token receives 401. Each token has a usage allowance; exceeding it returns 429 RATE_LIMITED with a Retry-After header — see errors & retries.

What still works after the subscription expires

  • Reads keep working. Listing projects, reading project detail and configuration, and reading post and comment leads continue under the same policy as website reads.
  • Writes follow the website’s rules. Configuration writes share the website’s plan gates: with enforcement enabled they answer 403 NO_ACTIVE_PLAN or a plan-limit problem, exactly like the website would. A denied write is a policy answer, not a credential failure.
  • Token expiry or revocation is different: such a key gets 401 on every request, including reads — check the dashboard list to see which situation you are in.
SituationResult
Valid token, read operation200 regardless of plan state
Valid token, write operation, plan lapsed (enforcement on)403 NO_ACTIVE_PLAN or a plan-limit problem, same as the website
Expired or revoked token401
Token on a website-only operation (e.g. billing, token management)401
Token usage allowance exhausted429 RATE_LIMITED + Retry-After

Next: the API reference for exact schemas — start with projects, then post leads.

Last updated on