> ## Documentation Index > Fetch the complete documentation index at: https://docs.eat-now.io/llms.txt > Use this file to discover all available pages before exploring further. # Get all active shifts > Returns all active, non-expired shifts for the authenticated restaurant. This endpoint is intentionally minimal and is primarily meant to expose usable shift identifiers for partner booking flows. `shift_type` is the underlying configuration type (`RECURRING` or `EVENT`). `reservation_mode` is derived from the current shift configuration: `AUTOMATIC` means no manual approval, `MANUAL` means every reservation requires staff approval, and `ADVANCED` means approval depends on the configured manual reservation threshold. `days_of_week`, `start_date`, and `end_date` are included so partners can determine when a shift is actually applicable. ## OpenAPI ````yaml https://app.eat-now.io/api/partner/v1/openapi.json get /api/partner/v1/shifts openapi: 3.0.3 info: title: EatNow Partner API version: v1 description: >- Version 1 of the EatNow partner API. This API is designed for trusted partner integrations that need restaurant-scoped access to availability, reservation management, and operational reference data. Authentication - Use `Authorization: Bearer ` with a partner API token created from the EatNow dashboard. - Access is controlled by credential scopes and each request is resolved to a single restaurant. Base URL - The server URL in this document is the canonical base URL for the current environment. Errors - Errors follow a consistent envelope with `error.code`, `error.message`, and `error.request_id`. - Validation, authentication, authorization, conflicts, and not-found cases all use the same top-level error shape. Rate limits - Partner API traffic is rate limited. Clients should treat `429` responses as retryable and back off accordingly. Public endpoints - `GET /api/partner/v1` and `GET /api/partner/v1/openapi.json` are public. - All business endpoints require Bearer authentication. servers: - url: https://app.eat-now.io security: [] tags: - name: Meta description: Platform metadata and schema endpoints - name: Authentication description: Credential validation and auth context endpoints - name: Availability description: Bookable slot search and exact slot validation - name: Catalog description: Reference data for restaurant tables, rooms, prescribers, and discounts - name: Reservations description: Reservation lookup, search, update, and cancellation - name: Missed Calls description: Report missed calls and trigger WhatsApp follow-up templates paths: /api/partner/v1/shifts: get: tags: - Catalog summary: Get all active shifts description: >- Returns all active, non-expired shifts for the authenticated restaurant. This endpoint is intentionally minimal and is primarily meant to expose usable shift identifiers for partner booking flows. `shift_type` is the underlying configuration type (`RECURRING` or `EVENT`). `reservation_mode` is derived from the current shift configuration: `AUTOMATIC` means no manual approval, `MANUAL` means every reservation requires staff approval, and `ADVANCED` means approval depends on the configured manual reservation threshold. `days_of_week`, `start_date`, and `end_date` are included so partners can determine when a shift is actually applicable. operationId: listPartnerCatalogShifts responses: '200': description: All active restaurant shifts ordered by configured order content: application/json: schema: $ref: '#/components/schemas/PartnerApiCatalogShiftListResponse' examples: default: summary: Active shift catalog value: data: - id: shift_dinner name: Dinner name_i18n: EN: Dinner FR: Diner shift_type: RECURRING days_of_week: - 1 - 2 - 3 - 4 - 5 start_date: null end_date: null start_time: '19:00' end_time: '23:00' reservation_mode: AUTOMATIC '401': description: Authentication failed content: application/json: schema: $ref: '#/components/schemas/PartnerApiError' '403': description: Scope is insufficient. The `CATALOG_READ` scope is required. content: application/json: schema: $ref: '#/components/schemas/PartnerApiError' security: - PartnerBearerToken: [] components: schemas: PartnerApiCatalogShiftListResponse: type: object properties: data: type: array items: $ref: '#/components/schemas/PartnerApiCatalogShift' required: - data PartnerApiError: type: object properties: error: type: object properties: code: $ref: '#/components/schemas/PartnerApiErrorCode' message: type: string request_id: type: string details: type: object additionalProperties: nullable: true required: - code - message - request_id required: - error PartnerApiCatalogShift: type: object properties: id: type: string name: type: string name_i18n: type: object properties: FR: type: string EN: type: string ES: type: string IT: type: string DE: type: string PT: type: string shift_type: type: string enum: - RECURRING - EVENT days_of_week: type: array items: type: integer start_date: type: string nullable: true end_date: type: string nullable: true start_time: type: string nullable: true end_time: type: string nullable: true reservation_mode: type: string enum: - AUTOMATIC - MANUAL - ADVANCED required: - id - name - name_i18n - shift_type - days_of_week - start_date - end_date - start_time - end_time - reservation_mode PartnerApiErrorCode: type: string enum: - AUTHENTICATION_REQUIRED - INVALID_AUTHENTICATION - INSUFFICIENT_SCOPE - VALIDATION_ERROR - RESOURCE_NOT_FOUND - RESOURCE_CONFLICT - RATE_LIMITED - INTERNAL_ERROR securitySchemes: PartnerBearerToken: type: http scheme: bearer bearerFormat: API Token description: >- Restaurant-scoped partner API token passed as `Authorization: Bearer `. x-default: your_token_here ````