Access keys

Integration keys, expiry and security-screening mode.

Integration keys, expiry and security-screening mode.

This screen belongs to the Router 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. Click Access keys → Create API key.
  2. Enter docs-staging, your tenant ID and the required expiry.
  3. Choose Strict Secure/Router for a protected integration; coordinate external access mode with the data owner.
  4. Create the key and place its one-time secret in the integration secret store.
  5. For rotation, prepare the client, rotate, copy the new key and update the client.

Every control and its meaning

Control / parameterValues, units and effect
Метка / LabelPurpose label, such as docs-staging. Do not put the secret in the label.
Tenant IDRequired; all requests are attributed to this tenant. Use an authorized identifier.
Срок действия / ExpiryEmpty means no expiry; a date limits validity. An expired key must be replaced.
policy_modeThe form offers strict screening and external_unrestricted external calls without screening. Configure external_masked through the supported API for mandatory replacement before external calls; there is no third form option.
Ротация / RevokeRotation immediately replaces the secret; revocation ends access. Bootstrap keys are managed by the operator.

Verify the result

Check a successful request and its tenant in history. The old secret should be denied after rotation/revocation; verify mode effects using synthetic data.

Errors, disabling and reverting changes

A closed one-time secret cannot be retrieved: create or rotate a key. For 401, check expiry/revocation and all clients. Reverting policy_mode does not restore a revoked secret.

API-key form · actual staging, no key created
API-key form · actual staging, no key created
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. Unsaved example; no new credential was created.
  1. Label
  2. Tenant ID
  3. Expiry
  4. Strict policy
  5. Create
API-key form · actual staging, no key created
API-key form · actual staging, no key created
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. Unsaved example; no new credential was created.
  1. Label
  2. Tenant ID
  3. Expiry
  4. Strict policy
  5. Create

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