The API Keys module centralizes the credentials that AI Gateway uses to authenticate with LLM provider APIs (OpenAI, Gemini, Anthropic, Azure OpenAI, and Bedrock). Each API Key is linked to a single provider and later referenced by LLM Providers.
NOTERegister API Keys before configuring LLM Providers. Each provider configuration requires an existing key.
Learn how to:
The API Keys page lists all registered credentials with pagination. You can filter by:
Use Search to apply the filter and Clear to reset it.
Columns shown in the table:
Fill in the Create API Key form fields (see Form fields).
In the Actions column of the row you want, click the Edit icon. The Update API Key form appears without the previously registered API Key value. The Provider field is immutable after registration. To change the provider, delete the current key and create a new one. Edit the API Key field and click Save.
In the Actions column of the row you want, click the Delete icon. Confirm the operation in the "Are you sure you want to delete this API key?" dialog.
IMPORTANTDeletion is permanent and cannot be undone. If an LLM Provider references the key, routes that depend on that provider start failing. Update or remove dependent configurations before deleting the key.
The table below covers all fields in the creation and edit forms.
Field | Type | Required | Rules |
|---|---|---|---|
| Provider | Select (enum) | Yes, only during creation | Values: OpenAI, Gemini, Anthropic, Azure OpenAI, Bedrock. Immutable after registration. |
| API Key | Text (sensitive) | Yes | Minimum 1 character, maximum 4096 characters. |
TIPThe gateway treats the key as sensitive information. No screen displays the key in plain text after registration, only the generated API Key ID.
We use cookies to enhance your experience on our site. By continuing to browse, you agree to our use of cookies.Learn more