API keys

Secure client keys, usage and revocation.

Secure client keys, usage and revocation.

This screen belongs to the Secure deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.

Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.

Step-by-step actions

  1. API keys → Create key (Создать ключ) opens the New API key dialog.
  2. Enter docs-staging, your Tenant ID and expiry.
  3. Create and store the one-time Bearer secret in the integration secret store.
  4. For rotation, open Rotate, check expiry, rotate and update the client secret.
  5. Use Revoke and confirm the specific key to end access.

Every control and its meaning

Control / parameterValues, units and effect
Label / Tenant IDLabel up to 120 characters, default api-key; Tenant ID required, form maximum 64. Key attributes inference to an organization.
Срок действия / ExpiryEmpty means no expiry; select today or later. The form converts the date to end-of-day expiry.
Usage / rotate / revokeUsage shows recorded calls; rotation immediately changes the secret; revocation denies access. Bootstrap entries are operator-managed.
Режим / ModeStandalone Secure does not expose Router policy_mode strict/external_unrestricted in this form. It is not a screening toggle.

Verify the result

Test a synthetic inspect call and tenant attribution; the old secret should be denied after rotation.

Errors, disabling and reverting changes

The secret cannot be retrieved after closing. For 401, check expiry/revocation and every client configuration; access recovery requires a valid new secret.

Secure API-key form · actual staging
Secure API-key form · actual staging
2026-10-15 · Actual staging application. Synthetic client, public definitions or aggregate test-stand metrics only; not customer statistics or a benchmark. Original pixels are unmodified; personal profile and private data excluded. The synthetic-tenant form was not submitted; no new key was created.
  1. Label
  2. Tenant ID
  3. Expiry
  4. Create key

Detailed security settings · Traffic analysis · FAQ · All application sections