Version: 1.0.0

SLO status v1.0

Get the status of your SLOs. For up-to-date features, use SLO status API v2.0.

SLO status API v1.0.0 is deprecated

This version will be sunset on Friday, January 30, 2026 12:00:00 GMT.

We recommend migrating to the SLO status API v2.0.0 as soon as possible.

When migrating to the latest SLO status API version, consider the following key changes:

Endpoint paths
- v1.0.0: /api/v1/slos and /api/v1/slos/{sloName}
- v2.0.0: /api/v2/slos and /api/v2/slos/{sloName}
Field structure: in v2.0.0, the project and service fields are returned as objects, instead of strings.
- v1.0.0 example: "project": "sample-project"
- v2.0.0 example:

{
  "project": {
    "name": "sample-project",
    "displayName": "Sample project",
    "labels": {
      "team": ["platform"]
    }
  }
}

Schema validation:
- Update integration code or parsing logic to handle the nested object structure for the project and service fields
Authentication and rate limits remain the same

Review your integrations for field structure dependencies and test requests against the v2.0.0 endpoints before the v1.0.0 sunset date.

All requests to the endpoint /api/v2/slos are rate-limited. An organization can make up to 10 requests per second.

The API returns 429 HTTP status code when this limit is exceeded.

Authentication required

Authenticate API requests using an access token. Include it in the Authorization header as Bearer TOKEN.

Authentication