Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.scaling.cloud/llms.txt

Use this file to discover all available pages before exploring further.

Every request to the Scaling API must include an API key. Scaling uses Bearer token authentication — you pass your API key in the Authorization header of each request.

​
API keys

API keys are scoped to your organization. Any request made with your key acts on behalf of your organization. Key format: 
scl_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

​
Get an API key

  1. Open the Scaling dashboard and go to Settings → API Access.
  2. Click Generate API key.
  3. Copy the key immediately — the full value is only shown once.
Store your API key in a secrets manager or environment variable. Never hardcode it in source code or commit it to version control.

​
Making authenticated requests

Include your API key as a Bearer token in the Authorization header: 
Authorization: Bearer scl_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Example request: 
curl https://api.scaling.cloud/v1/incidents \
  -H "Authorization: Bearer scl_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

​
Authentication errors

If your request is missing a valid API key, the API returns a 401 response.

​
Missing authorization header

Returned when the Authorization header is absent or does not start with Bearer . 
{
  "statusCode": 401,
  "type": "not_authorized_error",
  "code": "missing_authorization_header",
  "requestId": "550e8400-e29b-41d4-a716-446655440000"
}

​
Invalid API key

Returned when the token is present but invalid or expired. 
{
  "statusCode": 401,
  "type": "not_authorized_error",
  "code": "invalid_api_key",
  "requestId": "550e8400-e29b-41d4-a716-446655440000"
}
The requestId field is unique to each request. Include it when contacting support to help diagnose the issue.
Rotate your API key immediately if you suspect it has been exposed. Generate a new key from Settings → API Access and update any integrations that use the old key.