> ## Documentation Index > Fetch the complete documentation index at: https://developers.nexspace365.com/llms.txt > Use this file to discover all available pages before exploring further. # Get all shifts > Retrieve shifts with optional filtering by facility, date, status, or staff. **Required API-key scope:** `shifts:read` ## OpenAPI ````yaml https://api.nexspace365.com/api/openapi.json get /api/shifts openapi: 3.0.3 info: title: NexSpace 365 API description: > Multi-industry enterprise workforce management platform — scheduling, HR, payroll, CRM, AI, and messaging suites. ## Authentication Three schemes: session cookie, JWT bearer, or API key (`nex_live_…` / `nex_test_…` / `nex_pat_…`). AI agents should use API keys with appropriate scopes. ## Authorization Endpoints require specific permissions via the RBAC system: - **Internal team**: Full platform access - **Facility users**: Scoped to their org/facilities - **Staff**: Limited to own data ## Error Contract All errors return `{ error: { message, code?, suggestion?, retryable? }, requestId? }`. The `suggestion` field hints at how to fix the request; `retryable` signals whether retry-with-backoff is appropriate. ## Versioning Pin your integration to a specific API version via the `NexSpace-Version` header (date-based, e.g. `2026-05-10`). When absent, the latest version is assumed. Deprecated versions include `Sunset` and `Deprecation` headers. Discovery at `GET /.well-known/api-versions`. ## Idempotency Write operations (POST/PUT/PATCH) accept an `Idempotency-Key` header. If the same key + body combination is sent again within 24 hours, the original response is replayed. Different body with the same key returns 409 Conflict. ## MCP (Model Context Protocol) AI agents interact via `POST /mcp` using JSON-RPC 2.0. Call `tools/list` to discover available verbs, then `tools/call` to invoke them. version: 1.0.0 contact: name: NexSpace API Support email: support@nexspace365.com license: name: MIT url: https://opensource.org/licenses/MIT servers: - url: https://api.nexspace365.com description: Production server security: - bearerAuth: [] - apiKeyAuth: [] tags: - name: Authentication description: User authentication and session management - name: Facilities description: Facility management - name: Staff description: Staff member management and profiles - name: Credentials description: Staff credential tracking — licenses, certifications, and training - name: Shifts description: Shift scheduling and management - name: Dashboard description: Dashboard statistics and widgets - name: API Keys description: API key lifecycle — create, list, revoke, rotate - name: MCP description: Model Context Protocol endpoint for AI agent tool calling - name: OAuth description: OAuth 2.1 authorization server — DCR, authorize, token - name: Webhooks description: Outbound webhook subscription management - name: Analytics description: API usage analytics and observability paths: /api/shifts: get: tags: - Shifts summary: Get all shifts description: >- Retrieve shifts with optional filtering by facility, date, status, or staff. **Required API-key scope:** `shifts:read` operationId: listShifts parameters: - name: facilityId in: query description: Filter by facility ID schema: type: integer - name: date in: query description: Filter by specific date schema: type: string format: date - name: status in: query description: Filter by shift status schema: type: string enum: - open - assigned - in_progress - completed - cancelled - name: staffId in: query description: Filter by assigned staff member ID schema: type: integer - name: startDate in: query description: Filter from start date schema: type: string format: date - name: endDate in: query description: Filter to end date schema: type: string format: date responses: '200': description: List of shifts content: application/json: schema: type: array items: $ref: '#/components/schemas/Shift' '401': $ref: '#/components/responses/UnauthorizedError' '403': $ref: '#/components/responses/InsufficientScope' '429': $ref: '#/components/responses/RateLimited' security: - bearerAuth: [] - apiKeyAuth: [] components: schemas: Shift: type: object properties: id: type: integer description: Unique shift identifier facilityId: type: integer description: Facility where the shift takes place title: type: string description: Shift title or description date: type: string format: date description: Shift date startTime: type: string format: time description: Shift start time endTime: type: string format: time description: Shift end time department: type: string nullable: true description: Department for the shift specialty: type: string nullable: true description: Required specialty requiredWorkers: type: integer description: Number of workers needed assignedStaffIds: type: array items: type: integer description: IDs of assigned staff members status: type: string enum: - open - assigned - in_progress - completed - cancelled description: Current shift status urgency: type: string enum: - low - medium - high - critical description: Shift urgency level rate: type: number format: decimal nullable: true description: Pay rate for the shift notes: type: string nullable: true description: Additional notes or requirements createdAt: type: string format: date-time updatedAt: type: string format: date-time example: id: 1024 facilityId: 1 title: Evening Fulfillment date: '2026-05-20' startTime: '16:00' endTime: '23:59' department: Fulfillment specialty: Forklift Operator requiredWorkers: 3 assignedStaffIds: - 42 - 58 status: open urgency: high rate: 32 notes: Peak-season surge coverage createdAt: '2026-05-10T12:00:00Z' updatedAt: '2026-05-11T08:15:00Z' Error: type: object properties: error: type: object properties: message: type: string description: Human-readable error message code: type: string description: Machine-readable error code (e.g. VALIDATION_FAILED, NOT_FOUND) details: type: object description: Structured details (e.g. Zod validation issues) suggestion: type: string description: Hint for agents on how to recover retryable: type: boolean description: Whether the same request might succeed on retry required: - message requestId: type: string description: Correlation ID for logs and Sentry required: - error responses: UnauthorizedError: description: Missing, invalid, expired, or revoked credential. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: message: Invalid or revoked API key code: UNAUTHENTICATED suggestion: >- Send a valid `Authorization: Bearer ` (nex_live_/nex_pat_ key, JWT, or OAuth access token). retryable: false InsufficientScope: description: > Authenticated, but the API key's granted scopes do not include the scope this operation requires (see the operation's "Required API-key scope"). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: message: Insufficient API key scope code: INSUFFICIENT_SCOPE suggestion: >- Mint or rotate a key that includes the required scope, or grant a wildcard like `resource:*`. retryable: false RateLimited: description: > Per-key rate limit exceeded. Includes `Retry-After` and the full `X-RateLimit-*` set so agents can back off precisely (NEX-1659). headers: Retry-After: $ref: '#/components/headers/Retry-After' X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' content: application/json: schema: $ref: '#/components/schemas/Error' example: error: message: Rate limit exceeded for this API key code: API_KEY_RATE_LIMITED suggestion: >- Wait until X-RateLimit-Reset before retrying, or batch operations. retryable: true headers: Retry-After: description: Seconds to wait before retrying (present on 429). schema: type: integer X-RateLimit-Limit: description: Requests allowed per window for this API key (NEX-1659). schema: type: integer X-RateLimit-Remaining: description: Requests remaining in the current window. schema: type: integer X-RateLimit-Reset: description: Unix timestamp (seconds) when the current window resets. schema: type: integer securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: JWT token authentication apiKeyAuth: type: http scheme: bearer bearerFormat: NexSpaceApiKey description: | API key or personal access token (NEX-1042). Send as `Authorization: Bearer `. Token format: - `nex_live_…` — live API key (server-to-server) - `nex_test_…` — sandbox API key - `nex_pat_…` — personal access token (acts as the issuing user) Authorization is decided by the key's `scopes` array, not the owning user's RBAC role. See `POST /api/api-keys` to mint a key. ````