Account
API keys
Section titled “API keys”Developers → API Keys lists the account’s active keys with their name, type, masked secret, creation time and last use. Revoked keys are not listed.
Creating a key
Section titled “Creating a key”Press New key, give it a name (up to 64 characters) and choose a type. The secret is shown once, on creation; copy it then. Afterwards the dashboard only stores the first and last characters, which is what the list shows.
| Type | Prefix | Rate limit | Use it for |
|---|---|---|---|
| Live | sk_live_ |
60 requests a minute | Production traffic. |
| Test | sk_test_ |
20 requests a minute | Wiring up an integration. |
Both types run real searches against the same targets. One key per service makes it safe to rotate or revoke just that one.
Renaming a key
Section titled “Renaming a key”Changing the label does not touch the secret.
Rotating a key
Section titled “Rotating a key”Rotate revokes the key and mints a replacement with the same name and type. The new secret is shown once. The old secret stops authenticating within a minute, so update the service that holds it before you rotate.
Revoking a key
Section titled “Revoking a key”A revoked key stops authenticating within a minute. Its query history stays readable and it keeps appearing in usage breakdowns under its old name.
What a key cannot do
Section titled “What a key cannot do”A key authenticates the search endpoints only, GET /v1/query and
POST /v1/bulk. Usage reporting, query history and key management are
session-only: they refuse a bearer key, because a key that could mint another
key would make revoking the first one meaningless. Do those from the
dashboard.
Usage and history
Section titled “Usage and history”Dashboard shows requests, credits and error rate over the last 30 days, with a per-key breakdown. Search → History lists every query the account has run, newest first, filterable by key, target, date range and status; open a row for its parameters, outcome, timings and credits.