Skip to Content
Authentication

Authentication

Gateway API requests authenticate with Accly API keys.

Create an API key

API keys are created in the Accly app:

  1. Open chat.accly.net .
  2. Open settings.
  3. Go to API Keys.
  4. Create a new key.
  5. Copy the key immediately.

The full key is shown only once. If you lose it, create a new key.

Plan requirement

API keys are available on paid plans: Starter, Pro, and Max.

Free does not support API keys. If a paid subscription is suspended or the account is restricted, the gateway rejects API requests from existing keys.

Authorization header

Send the key in the Authorization header:

Authorization header
Authorization: Bearer sk-your-accly-api-key

Example:

curl
curl https://api.accly.net/v1/chat/completions \
  -H "Authorization: Bearer sk-your-accly-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "claude-opus-4-7",
    "messages": [{"role": "user", "content": "Hello"}]
  }'

Key types

When creating a key, choose the key type based on the API format your client or tool expects. The key type controls which protocol family or endpoint channel the key can use through the gateway.

Key typeEndpoint familyBest forNotes
openaiOpenAI-compatible endpointsOpenAI-compatible clients, agents, and /v1/chat/completionsBest default for most API users
anthropicAnthropic-style Messages APIAnthropic-native requests and tool behaviorUse when your integration expects Anthropic’s API shape
googleGoogle/Gemini-style Generate ContentGemini-native request formatUse when your integration expects Google’s API shape
universalOpenAI-compatible multi-model routingOne OpenAI-style interface for many supported modelsDoes not guarantee provider-native features

Universal lets you use many supported models through a common OpenAI-compatible interface, but provider-native endpoint behavior may require the matching provider key type.

Keep keys secret

Treat Accly API keys like passwords.

  • Never expose API keys in browser code or mobile client bundles.
  • Do not commit keys to Git.
  • Store keys in server-side environment variables or a secrets manager.
  • Use separate keys for separate apps or environments when possible.
  • Revoke keys you no longer use.

Rotate a leaked key

If a key is exposed:

  1. Revoke the key in the Accly app settings.
  2. Create a new key.
  3. Update your server, tool, or automation configuration.
  4. Review recent usage for unexpected activity.

Revoked keys are rejected by the gateway.