Skip to content
RouteAPI RouteAPI

Аутентификация

RouteAPI использует аутентификацию Bearer Token. Каждый API-запрос должен содержать действительный Token в заголовке Authorization.

Request header format

Section titled “Request header format”
Authorization: Bearer sk-your-routeapi-token

Пример:

Terminal window
curl https://www.routeapi.ai/v1/models \
  -H "Authorization: Bearer $ROUTEAPI_KEY"

API Token

Section titled “API Token”
  1. RouteAPI console.
  2. API Keys.
  3. Create token.
  4. Set name, quota, permissions, and expiration.
  5. Store it only on the server side or in a secure environment.

Token

Section titled “Token”
ConfigurationОписание
User balance402 may be returned when balance is insufficient
Token quotaA Token can have independent quota or expiration
Rate limit429 is returned after triggering

Рекомендации

Section titled “Рекомендации”
  • Do not expose Tokens in frontend code or public repositories.
  • Prefer environment variables for server-side calls.
  • Disable leaked Tokens immediately.

Common authentication errors

Section titled “Common authentication errors”
Status codeCauseHandling
401Missing or invalid TokenCheck Authorization
402Insufficient balance or quotaRecharge or adjust quota
429Rate limitReduce concurrency