Skip to main content
ErynoaGroup uses API key authentication for all API requests. Every call must include your API key in the Authorization header. This page is your API-level reference for authentication — for step-by-step key management instructions, see the Authentication guide.

Passing your API key

Include your API key as a Bearer token in the Authorization header:
Never pass API keys as query parameters. Always use the Authorization header to prevent keys from appearing in server access logs.

Key prefixes

ErynoaGroup API keys use prefixes to indicate environment: Using a production key against the sandbox API (or vice versa) returns a 401 Unauthorized error.

Key scopes

Each API key has a scope that limits what operations it can perform: Attempting an operation outside the key’s scope returns 403 Forbidden with error code insufficient_scope.

Authentication error reference

401 Unauthorized

Possible causes:
  • Key is missing from the request
  • Key contains a typo or extra whitespace
  • Key has been revoked from the dashboard

401 — Key expired

403 Forbidden

Resolution: Create a new key with the appropriate scope from Settings → API Keys.