> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sentivel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List maintenance windows

> The workspace's scheduled maintenance windows — the planned-work notices published on its public status pages — newest start first. `status` is where each window sits RIGHT NOW (scheduled | in_progress | completed | cancelled), derived from the clock, so a poller never has to recompute it from the timestamps.



## OpenAPI

````yaml https://www.sentivel.com/api/v1/openapi.json get /maintenance
openapi: 3.1.0
info:
  title: Sentivel API
  version: 1.0.0
  description: >-
    Provision and read your Sentivel workspace programmatically: components,
    monitors, status pages and incidents. Authenticate with an org API token
    (create one under Developers → API tokens in the dashboard).
  contact:
    name: Sentivel
    url: https://www.sentivel.com
servers:
  - url: https://www.sentivel.com/api/v1
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Identity
    description: Who the token is
  - name: Components
    description: Status-page components (status units)
  - name: Monitors
    description: Uptime/HTTP checks
  - name: Status pages
    description: Public status pages
  - name: Incidents
    description: Incidents (read + manual create)
  - name: People
    description: Workspace members
  - name: Integrations
    description: Outbound alert destinations
  - name: On-call
    description: On-call schedules
  - name: Maintenance
    description: Scheduled maintenance windows
paths:
  /maintenance:
    get:
      tags:
        - Maintenance
      summary: List maintenance windows
      description: >-
        The workspace's scheduled maintenance windows — the planned-work notices
        published on its public status pages — newest start first. `status` is
        where each window sits RIGHT NOW (scheduled | in_progress | completed |
        cancelled), derived from the clock, so a poller never has to recompute
        it from the timestamps.
      operationId: listMaintenance
      parameters:
        - name: page
          in: query
          description: Page number (1-indexed).
          schema:
            type: integer
            minimum: 1
            default: 1
        - name: per_page
          in: query
          description: Items per page (max 250).
          schema:
            type: integer
            minimum: 1
            maximum: 250
            default: 50
      responses:
        '200':
          description: The workspace's maintenance windows.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/Maintenance'
                  pagination:
                    $ref: '#/components/schemas/Pagination'
        '401':
          description: Unauthorized.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Maintenance:
      type: object
      properties:
        id:
          type: string
          format: uuid
        title:
          type: string
          description: The headline customers see.
        body:
          type: string
          description: The public explanation.
        status:
          type: string
          enum:
            - scheduled
            - in_progress
            - completed
            - cancelled
          description: >-
            Where the window sits right now. Derived from the clock — only
            `cancelled` is a stored state.
        startsAt:
          type: string
          format: date-time
        endsAt:
          type: string
          format: date-time
        components:
          type: array
          description: Components the window affects. Empty = the whole workspace.
          items:
            type: object
            properties:
              id:
                type: string
                format: uuid
              name:
                type: string
    Pagination:
      type: object
      properties:
        page:
          type: integer
        perPage:
          type: integer
        total:
          type: integer
        totalPages:
          type: integer
    Error:
      type: object
      properties:
        error:
          type: object
          properties:
            code:
              type: string
              enum:
                - unauthorized
                - forbidden
                - not_found
                - invalid_request
                - rate_limited
                - conflict
                - internal
            message:
              type: string
            details:
              type: object
          required:
            - code
            - message
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Sent as `Authorization: Bearer <token>`. Three kinds are accepted: an
        ORG token (`sv_…`), bound to one workspace with a fixed role; a PERSONAL
        token (`svu_…`), which acts as you with your own live role in whichever
        workspace it is pointed at; and an OAUTH access token (`mcp_at_…`) from
        a connected app, limited to the workspaces you granted it. A personal or
        OAuth token names its workspace with the `X-Sentivel-Workspace` header
        (a slug or an id). Without it an OAuth token falls back to the
        connection's primary workspace, while a personal token in more than one
        workspace is rejected `400 invalid_request` with the choices in
        `error.details.workspaces`. Membership is re-read every request, so
        leaving a workspace or revoking the grant takes effect at once.

````