---
title: "Get Capacity Schedules"
method: GET
path: "/v2/users/capacity/schedules"
tags: ["Routes", "Users", "Capacity", "Schedules"]
---

# Get Capacity Schedules

`GET /v2/users/capacity/schedules`

Returns per-user daily capacity rows for a date range, including applied precedence details.

Precedence order:
`exception > holiday > userSchedule > profileSchedule > default`.

Pagination:
- `cursor` is a zero-based offset.
- `limit` max is 100.

Date limits:
- `startDate` and `endDate` are required (YYYY-MM-DD).
- Date range cannot exceed 31 days.

Response notes:
- `range` now contains only `startDate` and `endDate`.
- `pagination` contains `cursor`, `limit`, `totalUsers`, and `nextCursor`.

## Query parameters

- `locations` string
- `users` string
- `startDate` string
- `endDate` string
- `cursor` integer
- `limit` integer

## Response `200`

Get Capacity Schedules

- object
  - `range` object
    - `startDate` string, date
    - `endDate` string, date
  - `locations` integer[]
  - `users` object[]
    - `userID` integer
    - `locations` integer[]
    - `days` object[]
      - `date` string, date
      - `capacityMinutes` integer
      - `hoursPerDay` integer
      - `minutesPerDay` integer
      - `isAvailable` boolean
      - `appliedRule` string
      - `reason` string
      - `reasonDetails` object
        - `scheduleID` integer
        - `profileID` unknown
  - `pagination` object
    - `cursor` integer
    - `limit` integer
    - `totalUsers` integer
    - `nextCursor` unknown

## Other responses

- `400` — A query parameter exceeds its allowed maximum (e.g. limit greater than 100).
- `401` — No `Authorization` header was provided on the request.
- `403` — The supplied credentials are invalid, the customer account is inactive, or the credentials do not have permission to perform this action.
- `429` — The per-minute or per-hour rate limit for this credential and method has been exhausted. Inspect the `X-RateLimit-*` headers to determine when to retry.
- `500` — An unhandled server-side error. The body message is generic (`System unavailable...`) when the underlying cause is a database fault; otherwise it reflects the raised error.

---

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