Authentication

All V1 endpoints require an API key.

Authorization: Bearer YOUR_API_KEY

Create and revoke keys in the Viggle Dashboard. Keep keys in server-side environment variables; never expose them in browser code, mobile apps, or public repositories.

Example

curl "https://apis.viggle.ai/v1/renders/render_xxx" \
  -H "Authorization: Bearer $VIGGLE_API_KEY"

Request IDs

Every response includes an X-Request-Id header. You may also provide your own value in the request. Include this ID when contacting support so we can trace the request.

curl "https://apis.viggle.ai/v1/renders/render_xxx" \
  -H "Authorization: Bearer $VIGGLE_API_KEY" \
  -H "X-Request-Id: checkout-render-42"

Authentication errors

V1 errors use one envelope:

{
  "error": {
    "code": "invalid_api_key",
    "message": "Invalid or expired API key",
    "request_id": "req_123abc"
  }
}

See Errors and recovery for handling guidance.

Get Started

Guides

Production

Example

Request IDs

Authentication errors

​Example

​Request IDs

​Authentication errors

Example

Request IDs

Authentication errors