Create an application API key

Connect an application to the corporate gateway and inspect its route.

Role: deployment operator. These steps use the operator console. An ordinary hosted account exposes only its own keys and limits; request policy, protection-mode and masking changes from the operator.

Before you start

You need console access and your organization’s existing Tenant ID. Personal users should open Router One.

Click path

  1. Sign in to the console and select the organization.
  2. Open Ключи доступа in the sidebar (/keys, page title API-ключи).
  3. Click Создать API-ключ; enter a purpose in Метка, such as docs-demo-client.
  4. Set the required Tenant ID to an existing tenant. This is different from the key label.
  5. Set Срок действия if needed. Keep Строгие правила Secure/Router for a policy-controlled corporate client.
  6. Click Создать and save the one-time full value in the client’s secret store.
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

Connect and verify

Use https://api.iamrouter.ru/v1 as the OpenAI-compatible base URL and the new key as Bearer authorization. Select an available model from Модели. Send a harmless request and locate it in История запросов. A visible form alone does not prove a key was created.

Recovery

A missing Tenant ID requires the organization identifier. For client 401, check key expiry and revocation. If a model is unavailable, check tenant permissions with the administrator.