VoidAI API Authentication

Most VoidAI API endpoints require a key or supported OAuth access token. The public model catalog at GET /v1/models and GET /v1/models/{id} does not require authentication.

Bearer authentication

Create a key in the dashboard. VoidAI API keys begin with sk-voidai-. Store yours in VOIDAI_API_KEY on your server.

curl https://api.voidai.app/v1/credits \
  -H "Authorization: Bearer $VOIDAI_API_KEY"

Authorized OAuth integrations can use their VoidAI OAuth access token with the same Bearer header. An OAuth token is not an API key; use the credential issued for your integration.

Anthropic-style header

The gateway also accepts x-api-key when no Authorization header is supplied:

curl https://api.voidai.app/v1/messages/count_tokens \
  -H "x-api-key: $VOIDAI_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"model":"claude-sonnet-4-6","messages":[{"role":"user","content":"Hello"}]}'

If both headers are present, Authorization takes precedence. An invalid Authorization header is not rescued by a valid x-api-key header.

Access checks

A valid credential does not grant access to every model. Account status, configured IP restrictions, balance, plan eligibility, and model-specific grants can affect a request. Claude models require additional account access; see the Claude usage disclosure. Keep credentials out of client-side code, source control, and logs. Manage or replace keys through your dashboard, and use separate credentials for separate integrations. See error handling when a request is rejected.

Getting Started

Guides

VoidAI API Authentication

Bearer authentication

Anthropic-style header

Access checks

​Bearer authentication

​Anthropic-style header

​Access checks

Bearer authentication

Anthropic-style header

Access checks