Skip to content

DocsDevelopers

Authentication and API keys

Create, use and revoke API keys.

Every request carries a workspace API key as a Bearer token. Keys start with ls_live_.

Header
Authorization: Bearer ls_live_…

Keep keys on your server or in your CI secrets, never in a browser or a mobile app. Each key belongs to one workspace and acts on that workspace only.

Creating and revoking keys#

  • Workspace owners and admins manage keys in Settings → API keys, on the Agency plan.
  • A workspace can have up to 20 active keys. Name each after where it runs, so you know which to revoke.
  • The key is shown once. We store only a hash of it, so a lost key cannot be shown again: create a new one.
  • Revoking takes effect at once: requests with that key get 401.

When authentication fails#

StatusCodeWhy
401unauthorizedThe key is missing, malformed, unknown, revoked or expired. The answer includes a WWW-Authenticate header.
403plan_requiredThe workspace's plan does not include the API (it is part of Agency).