Quick Start

This guide walks you through creating an account, generating an API key, and making your first API calls.

Create your account and organization

Go to scaling.cloud and sign up. During onboarding you’ll create an organization — this is the workspace that holds your incidents, schedules, and team members.All API keys and resources are scoped to your organization.

Get your API key

In the scaling.cloud dashboard, navigate to Settings → API Access and generate a new API key.Your key will look like this:

scl_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Copy it now — you won’t be able to see the full key again after leaving the page.

Keep your API key secure. Anyone with this key can create and manage incidents in your organization.

Create your first incident

Send a POST request to /v1/incidents with your API key in the Authorization header.

curl -X POST https://api.scaling.cloud/v1/incidents \
  -H "Authorization: Bearer scl_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Payment service latency spike",
    "description": "P99 latency above 2s for the past 10 minutes.",
    "severity": "high"
  }'

A successful response returns the created incident:

{
  "data": {
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "orgId": "org_2abc123def456",
    "title": "Payment service latency spike",
    "description": "P99 latency above 2s for the past 10 minutes.",
    "severity": "high",
    "status": "investigating",
    "escalationPolicyId": null,
    "createdBy": "user_2xyz789",
    "createdAt": "2026-04-07T10:00:00.000Z",
    "updatedAt": "2026-04-07T10:00:00.000Z"
  }
}

The id field is the incident’s unique identifier — save it to reference the incident in later requests.Severity levels: critical, high, medium, lowInitial status: All new incidents start with status investigating.

Check your incidents

Retrieve the list of incidents for your organization with a GET request:

curl https://api.scaling.cloud/v1/incidents \
  -H "Authorization: Bearer scl_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

The response includes your incidents and a pagination cursor:

{
  "data": {
    "incidents": [
      {
        "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
        "orgId": "org_2abc123def456",
        "title": "Payment service latency spike",
        "description": "P99 latency above 2s for the past 10 minutes.",
        "severity": "high",
        "status": "investigating",
        "escalationPolicyId": null,
        "createdBy": "user_2xyz789",
        "createdAt": "2026-04-07T10:00:00.000Z",
        "updatedAt": "2026-04-07T10:00:00.000Z"
      }
    ],
    "nextCursor": null
  }
}

When nextCursor is a string value, pass it as a query parameter to retrieve the next page of results.

Next steps

Authentication — Learn more about API keys and how to handle auth errors.
API Reference — Explore all available endpoints.

Authentication

Get Started

API Guides

Infrastructure as Code

AWS CloudWatch

Inbound Webhooks

MCP Server

Next steps

​Next steps

Next steps