Authentication

All Apodex APIs authenticate with an API key sent as a bearer token in the Authorization header.

How it works

Keys are created per account in the console and carry your full quota, so treat them as production credentials. Every request to the gateway is authenticated on its own — there is no session, no refresh, and no expiry unless you rotate the key.

Request header

curl https://api.apodex.ai/v1/chat/completions \
  -H "Authorization: Bearer $APODEX_API_KEY" \
  -H "Content-Type: application/json"

Create a key

Sign in to the console with email and password, or with Google.
Open API Keys and choose Create new key.
Copy the key into your secret store before closing the dialog.

The key is shown once and cannot be retrieved later. If you lose it, delete the key and create a new one.

Keys start with sk- followed by a base64 string:

sk-4f8Yt2Kq7Rw1mZx0Vb5nHj3cPl6sAe9dGuIoTrEwQkANk=

Send the header

Header	Value	Description
`Authorization` Required	`Bearer YOUR_API_KEY`	Your Apodex API key.
`Content-Type` Required	`application/json`	Must be application/json.

Keep keys safe

Never expose your API key in client-side code or public repositories
Rotate your API keys regularly
Use environment variables to store API keys
Monitor your API usage in the console