Authentication

Create API keys, scope them and authenticate requests.

Every API request is authenticated with a bearer token. Keys are created in the console under Settings, then API keys, and are shown once at creation time. Store them in your secret manager, never in source control.

Authenticating a request

curl https://api.gtalk2voip.com/v1/calls \
  -H "Authorization: Bearer $GTALK2VOIP_API_KEY"

Key types and scopes

• Live keys (prefix gk_live_) touch real carriers and are billable.
• Test keys (prefix gk_test_) route to the sandbox with simulated carrier behaviour.
• Scopes restrict a key to specific resources: calls:write, recordings:read, agents:write and so on. Create one key per service with the minimum scopes it needs.

Rotation

Two keys can be active at once. Create the replacement key, deploy it, then revoke the old one. Revocation takes effect within 60 seconds everywhere.

Failure responses

{
  "error": {
    "type": "authentication_error",
    "message": "API key revoked on 2026-07-01.",
    "doc_url": "https://gtalk2voip.com/docs/authentication"
  }
}