Skip to main content
Create API keys in Mission Control Portal. An API key authenticates server-side REST API requests for the associated Telnyx account.

​
Create a key

  1. Open API Keys in Mission Control Portal and sign in.
  2. Select Create API Key.
  3. Add a descriptive label that identifies the environment and application.
  4. Under Expiration, select No Expiration or Set Expiration Date.
  5. Create the key.
  6. Copy the value immediately.
The key value is displayed onceStore the new value before leaving the creation dialog. If the value is lost, create a replacement key. Do not send the key in email, tickets, or chat.

​
Store the key

Use a secret manager for deployed applications. For local development, export a protected environment variable:
  • Keep .env and local secret files out of Git.
  • Restrict secret-manager access to required application runtimes and operators.
  • Redact Authorization headers from application and proxy logs.
  • Use separate keys for development, staging, and production.

​
Validate a key

Continue with Make the first API request for the response contract and failure handling.

​
Rotate a key

For a key with an expiration date, deploy a replacement before the date shown in the Expires column in Mission Control Portal.
  1. Create and store a replacement key.
  2. Deploy the replacement to every runtime that uses the old key.
  3. Confirm a read-only authenticated request succeeds from the updated runtime.
  4. Revoke the old key from API Keys in Mission Control Portal.
  5. Monitor authentication failures for workloads that still reference the old value.
Revoke a key immediately after suspected exposure. Rotation does not remove leaked values from repository history or logs; remove or redact those copies separately.

​
Use SDKs or CLI

Current constructors, installation commands, and first requests are maintained in the server-side SDK guides. CLI authentication is documented in the Telnyx CLI guide.