Authenticate with Inferoute

​

Generate an API key

1. Sign in to your Inferoute dashboard at inferoute.ai.
2. Go to Settings → API Keys.
3. Click New API key.
4. Enter a descriptive name for the key (for example, production-app or dev-local).
5. Optionally set an expiry date to limit how long the key remains valid.
6. Click Create and copy the key immediately — it will not be shown again.

​

Pass the API key in requests

import os
from openai import OpenAI

client = OpenAI(
    base_url="https://api.inferoute.ai/v1",
    api_key=os.environ["INFEROUTE_API_KEY"],
)

response = client.chat.completions.create(
    model="gpt-4o-mini",
    messages=[{"role": "user", "content": "Hello"}],
)

import OpenAI from "openai";

const client = new OpenAI({
  baseURL: "https://api.inferoute.ai/v1",
  apiKey: process.env.INFEROUTE_API_KEY,
});

const response = await client.chat.completions.create({
  model: "gpt-4o-mini",
  messages: [{ role: "user", content: "Hello" }],
});

curl https://api.inferoute.ai/v1/chat/completions \
  -H "Authorization: Bearer $INFEROUTE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-4o-mini",
    "messages": [{ "role": "user", "content": "Hello" }]
  }'

​

Use environment variables

export INFEROUTE_API_KEY="your_api_key_here"

​

Invalid and expired keys

{
  "error": {
    "message": "Invalid API key provided.",
    "type": "authentication_error",
    "code": "invalid_api_key"
  }
}

• The Authorization header is present and uses the Bearer prefix.
• The key was copied correctly with no leading or trailing whitespace.
• The key has not expired (check Settings → API Keys in the dashboard).
• The key has not been revoked.

​

Security best practices

• Use environment variables — never hardcode an API key in source code or configuration files.
• Never commit keys to version control — add .env and any secrets files to your .gitignore.
• Create separate keys per environment — use distinct keys for development, staging, and production so you can revoke one without affecting the others.
• Set expiry dates — use short-lived keys for CI pipelines and temporary integrations.
• Rotate keys regularly — revoke and replace keys periodically, especially after a team member leaves or a potential exposure.
• Limit key scope — if your use case allows, create keys with restricted permissions rather than full-access keys.

​

Manage your API keys