Skip to main content
API keys authenticate requests made to the 1eye API. Each key belongs to a workspace and inherits that workspace’s rate limits.

​
About API keys

  • Keys use the format 1eye_live_… and are passed as a Bearer token in the Authorization header
  • A new key’s full value is shown exactly once, at creation — copy it somewhere safe right away
  • After that, keys are shown in a masked format, like 1eye_live_••••••••8f21
  • A key is either active or revoked — once revoked, a key cannot be restored

​
Create an API key

  1. Open your 1eye workspace and go to Developers > API Keys
  2. Select New API Key
  3. Give the key a descriptive name, such as Prod Key or Staging Key
  4. Copy the full key value shown — it will not be shown again

​
Using your API key

Pass the key as a Bearer token in the Authorization header of every request:

​
Revoke a key

Revoking a key immediately blocks it from authenticating further requests. This cannot be undone.
  1. Go to Developers > API Keys
  2. Find the key and select Revoke
  3. Confirm the action

​
If you lose a key

A key’s full value can’t be retrieved again after creation. If a key is lost or exposed, don’t try to recover it — replace it:
  1. Create a new API key
  2. Update your integration to use the new key
  3. Revoke the old key

​
Best practices

  • Use separate keys per environment — Create distinct keys for production, staging, and testing so you can revoke one without affecting the others.
  • Name keys clearly — Use names like Prod Key or Staging Key so your team knows what each key is used for.
  • Revoke keys you no longer use — Remove unused or old keys instead of leaving them active.
  • Never share a key in plain text — store it in a secrets manager or environment variable, not in code or chat

​
Next step

Next, go to API Logs to review requests made with your keys.Create, manage, and revoke the API keys your integrations use to authenticate with the 1eye API.