---
title: "Get a maintenance"
method: GET
path: "/maintenance/{id}"
tags: ["maintenance"]
---

# Get a maintenance

`GET /maintenance/{id}`

## Path parameters

- `id` string, required — The id of the maintenance

## Response `200`

Get a maintenance

- Maintenance
  - `id` number, required — The id of the maintenance
  - `title` string, required — The title of the maintenance
  - `message` string, required — The message describing the maintenance
  - `from` string, date, nullable, required — When the maintenance starts
  - `to` string, date, nullable, required — When the maintenance ends
  - `monitorIds` number[] — IDs of affected monitors
  - `pageId` number, required — The id of the status page this maintenance belongs to

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
- `401` — The client must authenticate itself to get the requested response.
- `402` — A higher pricing plan is required to access the resource.
- `403` — The client does not have the necessary permissions to access the resource.
- `404` — The server can't find the requested resource.
- `409` — The request could not be completed due to a conflict mainly due to unique constraints.
- `500` — The server has encountered a situation it doesn't know how to handle.

---

[API](https://skmtc.net/openstatus/apis/openstatus-api.md) · [All operations](https://skmtc.net/openstatus/apis/openstatus-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/openstatus/openstatus-api/revisions/f075fbb509f7/schema)
