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

# Get checkout dates

> Returns possible checkout dates for a selected check-in date.

The response contains only checkout dates with continuous prices from the selected check-in date through the check-out date and respects the visit type's allowed stay lengths and date ranges. Capacity does not filter these choices: a valid priced stay can continue as an `ON_DEMAND` request. Use the booking configuration response to determine final availability. The check-out date is not charged and does not consume capacity, but it must be covered by the continuous pricing range.




## OpenAPI

````yaml /api/v1/openapi.yaml get /calendar/checkouts
openapi: 3.0.3
info:
  title: SpaPortal API v1
  version: '1.0'
  description: Public API for booking clients that integrate with SpaPortal.
servers:
  - url: https://spaportal.cz/api/v1
    description: Production
security:
  - bearerAuth: []
  - accessTokenQuery: []
tags:
  - name: System
  - name: Catalog
  - name: Availability
  - name: Pricing
  - name: Booking
paths:
  /calendar/checkouts:
    get:
      tags:
        - Availability
      summary: Get checkout dates
      description: >
        Returns possible checkout dates for a selected check-in date.


        The response contains only checkout dates with continuous prices from
        the selected check-in date through the check-out date and respects the
        visit type's allowed stay lengths and date ranges. Capacity does not
        filter these choices: a valid priced stay can continue as an `ON_DEMAND`
        request. Use the booking configuration response to determine final
        availability. The check-out date is not charged and does not consume
        capacity, but it must be covered by the continuous pricing range.
      operationId: getCalendarCheckouts
      parameters:
        - $ref: '#/components/parameters/AcceptLanguage'
        - name: start_date
          in: query
          required: true
          schema:
            type: string
            format: date
          description: Check-in date in `YYYY-MM-DD` format.
        - name: visit_type_id
          in: query
          schema:
            type: integer
          description: Visit type ID.
        - name: hotel_id
          in: query
          schema:
            type: integer
          description: Hotel ID.
        - name: room_type_id
          in: query
          schema:
            type: integer
          description: Room type ID.
      responses:
        '200':
          description: Valid checkout dates.
          headers:
            Content-Language:
              $ref: '#/components/headers/ContentLanguage'
          content:
            application/json:
              schema:
                type: array
                items:
                  type: object
                  properties:
                    date:
                      type: string
                      format: date
              examples:
                default:
                  $ref: '#/components/examples/CalendarCheckoutsResponse'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
        '422':
          $ref: '#/components/responses/UnprocessableEntity'
components:
  parameters:
    AcceptLanguage:
      name: Accept-Language
      in: header
      schema:
        type: string
        example: cs_CZ,de
      description: >-
        Comma-separated list of languages to include. See
        [Localization](/api/v1/localization) for details.
  headers:
    ContentLanguage:
      description: Languages included in the response.
      schema:
        type: string
        example: cs_CZ,de
  examples:
    CalendarCheckoutsResponse:
      summary: Checkout dates
      value:
        - date: '2026-12-09'
        - date: '2026-12-16'
  responses:
    BadRequest:
      description: Invalid request.
      content:
        application/json:
          schema:
            oneOf:
              - $ref: '#/components/schemas/ErrorResponse'
              - $ref: '#/components/schemas/ValidationErrorResponse'
    Unauthorized:
      description: Invalid API key.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    NotFound:
      description: Resource not found.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    UnprocessableEntity:
      description: Resource exists but cannot be used for this request.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  schemas:
    ErrorResponse:
      type: object
      required:
        - success
        - message
      properties:
        success:
          type: boolean
          example: false
        message:
          type: string
    ValidationErrorResponse:
      type: object
      required:
        - success
        - message
        - errors
      properties:
        success:
          type: boolean
          example: false
        message:
          type: string
        errors:
          type: array
          items:
            type: object
            additionalProperties: true
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        See [Authentication](/api/v1/authentication) for how to obtain and send
        your API key.
    accessTokenQuery:
      type: apiKey
      in: query
      name: access_token
      description: >-
        See [Authentication](/api/v1/authentication) for how to obtain and send
        your API key.

````