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

# List every review linked to a booking

> Every review linked to this booking, newest first, in both directions and unpaginated.

Do not assume at most two. The strict `POST /bookings/{bookingId}/reviews` route allows one review per direction, but the older project-level `POST /reviews` accepts a `bookingId` without deduplicating, so a booking created through that path can carry several client→supplier reviews. Read the list, do not index into it.

Each review carries best-effort `supplierName` / `clientName` resolved from the two profiles, so a hosted review page renders without further calls; a counterparty that cannot be resolved keeps its bare id and those fields are absent. No email address is returned for either party. An unknown booking returns 404, matching the POST.



## OpenAPI

````yaml /api-reference/openapi.json get /v1/projects/{projectId}/bookings/{bookingId}/reviews
openapi: 3.0.0
info:
  title: MarketBox 2.0 Open API
  version: 1.0.0
  description: >-
    The MarketBox public API for building booking experiences. Core model:
    create an order, then draw its order items down into bookings. Single
    bookings reference an order item per service line; package bookings draw one
    PACKAGE item down across N sessions. To schedule a package, build a slate
    (POST /availability/package-slate) and book it by slateId (POST
    /orders/{orderId}/package-bookings). See the guides for end-to-end
    walkthroughs.
  contact:
    name: MarketBox support
servers:
  - url: https://apiv2.gomarketbox.com
    description: MarketBox Open API
security:
  - ApiKeyAuth: []
paths:
  /v1/projects/{projectId}/bookings/{bookingId}/reviews:
    get:
      tags:
        - Reviews
      summary: List every review linked to a booking
      description: >-
        Every review linked to this booking, newest first, in both directions
        and unpaginated.


        Do not assume at most two. The strict `POST
        /bookings/{bookingId}/reviews` route allows one review per direction,
        but the older project-level `POST /reviews` accepts a `bookingId`
        without deduplicating, so a booking created through that path can carry
        several client→supplier reviews. Read the list, do not index into it.


        Each review carries best-effort `supplierName` / `clientName` resolved
        from the two profiles, so a hosted review page renders without further
        calls; a counterparty that cannot be resolved keeps its bare id and
        those fields are absent. No email address is returned for either party.
        An unknown booking returns 404, matching the POST.
      parameters:
        - schema:
            type: string
            minLength: 1
            description: >-
              The project (tenant) that owns the resource. Every resource in
              this API is scoped to a project, and your API key is restricted to
              the projects it was issued for — a project outside that scope
              returns 403.
            example: prj_01kv60qgnef2kt3pvqgwmkbzfr
          required: true
          description: >-
            The project (tenant) that owns the resource. Every resource in this
            API is scoped to a project, and your API key is restricted to the
            projects it was issued for — a project outside that scope returns
            403.
          name: projectId
          in: path
        - schema:
            type: string
            minLength: 1
            description: >-
              The booking — one scheduled unit of service occupying supplier
              time.
            example: bk_01kv7q41n2hbqxwm03ymn7bxl9
          required: true
          description: The booking — one scheduled unit of service occupying supplier time.
          name: bookingId
          in: path
      responses:
        '200':
          description: Reviews for the booking
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      type: object
                      properties:
                        reviewId:
                          type: string
                        supplierId:
                          type: string
                        clientId:
                          type: string
                        projectId:
                          type: string
                        ratingStars:
                          type: integer
                        reviewText:
                          type: string
                        reviewerId:
                          type: string
                        bookingId:
                          type: string
                        direction:
                          type: string
                          enum:
                            - CLIENT_TO_SUPPLIER
                            - SUPPLIER_TO_CLIENT
                        subjectType:
                          type: string
                          enum:
                            - SUPPLIER
                            - CLIENT
                        subjectId:
                          type: string
                        createdAt:
                          type: string
                        supplierName:
                          type: string
                        clientName:
                          type: string
                      required:
                        - reviewId
                        - supplierId
                        - projectId
                        - ratingStars
                        - direction
                        - subjectType
                        - subjectId
                        - createdAt
                required:
                  - data
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorMessage'
        '403':
          description: API key cannot access this project
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorMessage'
        '404':
          description: Booking not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorMessage'
components:
  schemas:
    ErrorMessage:
      type: object
      properties:
        code:
          type: string
          description: Stable machine-readable error code, e.g. NOT_FOUND.
        message:
          type: string
          description: Human-readable description of what went wrong.
        statusCode:
          type: integer
          description: The HTTP status code of this response.
        requestId:
          type: string
          description: >-
            The id of this request, also returned as the X-Request-Id header.
            Quote it in a support ticket.
      required:
        - code
        - message
        - statusCode
        - requestId
      example:
        code: NOT_FOUND
        message: Booking not found
        statusCode: 404
        requestId: a3f1c2de-9b64-4a2f-8f0e-5c9d1b7a2e10
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        API key minted in the MarketBox dashboard. Scope is restricted to the
        projects you select at creation time. Every route needs the key's
        standard API access (`*`) except `POST /v1/projects/{projectId}/events`,
        which needs `events:write`; a key without `*` is refused with 403
        `CAPABILITY_NOT_GRANTED`.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.