openapi: "3.1.0"
info:
  title: Mermaid support Demo
  description: |
    This is an example of how using Mermaid can help you add context to your documentation. [You can see our dedicated help center section here](https://docs.bump.sh/help/enhance-documentation-content/markdown-support/).
  version: "1.0"
servers:
  - url: https://example.com/api/v1
x-topics:
  - title: Roadmap
    content: |
      Here’s a quick overview of our next focus regarding our different endpoints.

      ```mermaid
      gantt
        title Development timeline
        dateFormat YYYY-MM-DD
          section Booking API
            Development:a1, 2025-01-15, 30d
            Open beta:after a1, 20d
          section Payment API
            Development:b1, 2025-01-25, 12d
            Open beta:after b1, 20d
      ```
paths:
  /booking/{id}:
    get:
      summary: Fetch detailed information from an existing booking
      description: |
        ## Technical flow 
        ```mermaid
        erDiagram
          CUSTOMER }|..|{ DELIVERY-ADDRESS : has
          CUSTOMER ||--o{ ORDER : places
          CUSTOMER ||--o{ INVOICE : "liable for"
          DELIVERY-ADDRESS ||--o{ ORDER : receives
          INVOICE ||--|{ ORDER : covers
          ORDER ||--|{ ORDER-ITEM : includes
          PRODUCT-CATEGORY ||--|{ PRODUCT : contains
          PRODUCT ||--o{ ORDER-ITEM : "ordered in"
        ```
      parameters:
        - in: path
          name: id
          schema:
            type: string
            description: UUID of an existing booking
          required: true
          description: UUID of an existing booking from which to fetch diff details
      responses:
        "201":
          description: "Booking successfully retrieved"
          content:
            "application/json":
              schema:
                type: object
                properties:
                  id:
                    type: string
                    description: "Unique id of your booking"
                    example: d6f00a51-a175-4a44-a0c7-df62a48548ca