Skip to main content
An APIONE API Key authorizes inference requests; it is not your console password. Send it in request headers from your server and keep it out of browser code, screenshots, and logs.
APIONE API Key settings, connection addresses, and pricing groups.

APIONE API Key settings, connection addresses, and pricing groups.

Create and save a key

  1. Sign in to the APIONE console.
  2. Open API Keys and create a key for your application.
  3. Set the available model permissions, billing group, and expiration options shown in the console. Save the complete key when it is displayed.
  4. Send a minimal quickstart request to verify access.

Groups and permissions

The selected group determines available models and their prices. After creating or editing a key, query GET /v1/models before making application requests. See model discovery and group pricing.

Authentication

OpenAI-compatible requests use Authorization: Bearer YOUR_APIONE_KEY. Anthropic-compatible requests can use x-api-key. Use one authentication method per request.
  • Separate development, testing, and production keys to simplify usage tracking and rotation.
  • Store credentials in environment variables or a server-side secret manager, not frontend code or public configuration.
  • Log aliases or redacted identifiers instead of full keys and headers.
  • If a key is exposed, disable or revoke it in the console, configure a replacement, and verify recovery using available management controls.

Rotation checklist

Check health requests, model permissions, and error rates after deployment. Confirm all instances have switched before retiring the old key. If rotation fails, provide request IDs and redacted configuration to support rather than credentials. Related: Usage and costs, Contact support.