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

# List a booking's add-on allocations

> Lists a booking's participant add-on allocations, including participant and line-item references, product and variant details, and operational and financial status.

<Warning>This endpoint is restricted and not generally available: organizations that have not been enabled receive a `403`. Contact your Let's Do This representative if you'd like access.</Warning>


## OpenAPI

````yaml /openapi.json get /v0/bookings/{id}/add-on-allocations
openapi: 3.1.0
info:
  title: Let's Do This API
  version: 0.1.0
  description: >
    The full reference — getting started, pagination, error responses, rate
    limits and the changelog — lives at

    [partner-help.letsdothis.com/api-reference](https://partner-help.letsdothis.com/api-reference/overview).

    This page is the interactive OpenAPI view of the same specification.


    # Authentication


    Create an API key from **Settings** → **Credentials** in your Let's Do This
    account and send it as a bearer token:


    ```bash

    curl --request GET \
     --url "https://api.letsdothis.com/v0/participants" \
     --header "Authorization: Bearer YOUR-API-KEY"
    ```


    Keep the key secret: it identifies your organization, so do not ship it in a
    website or native app. If a key is exposed,

    revoke it from the same section and create a replacement.


    # OpenAPI schema


    Download the [OpenAPI schema](https://api.letsdothis.com/documentation/json)
    to use with Postman or an OpenAPI client

    generator.
servers:
  - url: https://api.letsdothis.com
    description: Production
  - url: https://api.staging.letsdothis.com
    description: Staging
security:
  - bearerAuth: []
tags:
  - name: Events
    x-group: Events
    description: Events that participants can register for.
  - name: EventOccurrences
    x-group: Event occurrences
    description: >-
      Event occurrences scoped to the organizer associated with your Public API
      credentials. Unlike the public Events catalog, results are limited to your
      own events.
  - name: Races
    x-group: Races
    description: >-
      Races within an event occurrence. An event occurrence may have one or more
      races, for example a 5K and a 10K within the same race day.
  - name: Tickets
    x-group: Tickets
    description: Tickets that are available for events.
  - name: BookingForms
    x-group: Booking forms
    description: >-
      Booking forms define the questions a booker answers when registering for a
      ticket. A ticket usually references a single booking form, so expect zero
      or one, while a booking form may be shared across multiple tickets.
  - name: BookingFormFields
    x-group: Booking form fields
    description: >-
      Booking form fields are the individual questions on a booking form — their
      type, label, options, and whether an answer is required. A field can be
      reused across multiple forms.
  - name: Bookings
    x-group: Bookings
    description: >-
      Bookings are the transaction record for a registration. A booking may
      contain one or more participants (entries).
  - name: Participant
    x-group: Participants
    description: Participants are users who successfully booked an event.
  - name: LineItem
    x-group: Line items
    description: Financial details related to individual items within transactions.
  - name: AddOns
    x-group: Add-ons
    description: >-
      Organizer-owned products that can be purchased and allocated to
      participants. Imported products retain stable external identities.
  - name: DiscountCodes
    x-group: Discount codes
    description: >-
      Discount codes participants enter at checkout to reduce the price of a
      booking.
  - name: Credits
    x-group: Credits
    description: >-
      Credits are balances participants can spend at checkout, identified by
      their email address.
  - name: Referrals
    x-group: Referrals
    description: >-
      Referral programs, the referrers registered on them, and asynchronous
      imports of historical referrals.
  - name: Application
    x-group: Applications
    description: >-
      Applications are created when a user applies for tickets that are set up
      to require an application process, such as balloted or "Good For Age"
      entries.
  - name: Partner
    x-group: Partners
    description: >-
      Partners that were created by the organization who can have Reserved
      Entries assigned to them.
  - name: ReservedEntries
    x-group: Reserved entries
    description: >-
      Reserved Entries are entries that are reserved for a partner. After being
      assigned, the partner can then allocate these entries to participants.
  - name: Timing
    x-group: Timing
    description: >-
      Timing providers push bib numbers and bib-pack shipments back to Let's Do
      This for the startlist entries they received. Available to select timing
      partners only.
paths:
  /v0/bookings/{id}/add-on-allocations:
    get:
      tags:
        - AddOns
      summary: List a booking's add-on allocations
      description: >-
        Lists a booking's participant add-on allocations, including participant
        and line-item references, product and variant details, and operational
        and financial status.
      parameters:
        - schema:
            type:
              - number
              - 'null'
            minimum: 1
            maximum: 500
            example: 100
          in: query
          name: page[size]
          required: false
          description: >-
            The number of entries to return per page. Range between 1 - 500,
            defaults to 100
        - schema:
            type:
              - string
              - 'null'
          in: query
          name: page[after]
          required: false
          description: >-
            Accepts an existing page cursor. For more details see the definition
            of PageCursor in the response.
        - schema:
            type:
              - string
              - 'null'
          in: query
          name: page[before]
          required: false
          description: >-
            Accepts an existing page cursor. For more details see the definition
            of PageCursor in the response.
        - schema:
            type: string
          example: '67123'
          in: path
          name: id
          required: true
          description: The ID of the resource to query by
      responses:
        '200':
          description: Default Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PagedBookingAddOnAllocations'
        '404':
          description: Not found
          content:
            application/json:
              schema:
                description: Not found
                type: object
                properties:
                  statusCode:
                    type: number
                    enum:
                      - 404
                  error:
                    type: string
                  message:
                    type: string
components:
  schemas:
    PagedBookingAddOnAllocations:
      title: PagedBookingAddOnAllocations
      type: object
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/BookingAddOnAllocation'
        page:
          $ref: '#/components/schemas/PageCursor'
      required:
        - data
        - page
      additionalProperties: false
      description: >-
        A cursor-paginated list of participant add-on allocations associated
        with a booking.
    BookingAddOnAllocation:
      title: BookingAddOnAllocation
      type: object
      properties:
        id:
          type: string
        bookingId:
          type: string
        participantId:
          type:
            - string
            - 'null'
          description: >-
            Nullable for legacy allocation records; new imports require a
            participant.
        purchaseLineItemId:
          type: string
        externalLineItemId:
          type: string
        addOn:
          anyOf:
            - $ref: '#/components/schemas/BookingAddOnAllocationProduct'
            - type: 'null'
          description: >-
            Null when the historical variant no longer resolves to a readable
            product.
        variant:
          $ref: '#/components/schemas/BookingAddOnAllocationVariant'
        status:
          $ref: '#/components/schemas/BookingAddOnAllocationStatus'
        financialStatus:
          $ref: '#/components/schemas/BookingAddOnAllocationFinancialStatus'
        createdAt:
          $ref: '#/components/schemas/ISODate'
        updatedAt:
          $ref: '#/components/schemas/ISODate'
      required:
        - id
        - bookingId
        - participantId
        - purchaseLineItemId
        - addOn
        - variant
        - status
        - financialStatus
        - createdAt
        - updatedAt
      additionalProperties: false
      description: One stored participant add-on allocation belonging to a booking.
      example:
        id: 65c3d4e5f60718293a4b5c6d
        bookingId: 65a1b2c3d4e5f60718293a4b
        participantId: 8c11d86e-a472-4d4a-b1aa-0a816f715f21
        purchaseLineItemId: 65b2c3d4e5f60718293a4b5c
        externalLineItemId: order-1042-tshirt
        addOn:
          id: 5fcd4b7e-1a2c-4d89-8f31-6b72e09a45c3
          externalAddOnId: city-marathon-tshirt
          name: City Marathon Technical T-shirt
        variant:
          id: 29bb39a4-3206-4f43-9a6a-79d83fc1c31e
          externalVariantId: city-marathon-tshirt-navy-m
          name: Navy / Medium
        status: ALLOCATED
        financialStatus: PAID
        createdAt: '2025-04-18T14:30:00.000Z'
        updatedAt: '2025-04-18T14:30:00.000Z'
    PageCursor:
      title: PageCursor
      type: object
      properties:
        totalResults:
          type: number
          description: The total number of results available.
        first:
          type: string
          description: The cursor for the first page of results.
        last:
          type: string
          description: The cursor for the last page of results.
        prev:
          type: string
          description: The cursor for the previous page of results.
        next:
          type: string
          description: The cursor for the next page of results.
      required:
        - totalResults
        - first
        - last
        - prev
        - next
      additionalProperties: false
      description: >-
        **Cursor details for pagination**.

        - In scenarios with large amounts of data, it's common to return only a
        subset of data in a single request, known as a "page".

        - Most API responses include two objects: a 'data' object with the query
        results, and a 'PageCursor' object detailing the current page.

        - Cursors can be used to navigate to earlier or later pages in the set
        of results. For instance, passing the 'next' cursor from 'PageCursor'
        fetches the next set of results.

        - Cursors are base64 encoded strings.
      example:
        totalResults: 506
        first: >-
          eyJpZCI6IjYzOTljMjAwMTVkNjBhZTNmZjI4ZjI0YyIsInVwZGF0ZWRBdCI6IjIwMjItMTItMTRUMTI6MzA6NTkuMjE3WiJ9
        last: >-
          eyJpZCI6IjY1NGNkZDIxZDlhMTU3ODdiNzFkMTM0YSIsInVwZGF0ZWRBdCI6IjIwMjMtMTEtMTNUMTU6MTE6MTIuNzI0WiJ9
        prev: ''
        next: >-
          eyJpZCI6IjY0NzBkNTkwM2RjOWE5OWJhMTA0Y2ZhYiIsInVwZGF0ZWRBdCI6IjIwMjMtMTEtMTNUMTU6MTE6MTIuNjE4WiJ9
    BookingAddOnAllocationProduct:
      title: BookingAddOnAllocationProduct
      type: object
      properties:
        id:
          type: string
        externalAddOnId:
          type: string
        name:
          type:
            - string
            - 'null'
          description: Null when the historical catalog row can no longer be resolved.
      required:
        - id
        - name
      additionalProperties: false
    BookingAddOnAllocationVariant:
      title: BookingAddOnAllocationVariant
      type: object
      properties:
        id:
          type: string
        externalVariantId:
          type: string
        name:
          type:
            - string
            - 'null'
          description: Null when the historical catalog row can no longer be resolved.
      required:
        - id
        - name
      additionalProperties: false
    BookingAddOnAllocationStatus:
      title: BookingAddOnAllocationStatus
      type:
        - string
        - 'null'
      enum:
        - ALLOCATED
        - CANCELLED
        - null
      description: Operational state stored for a participant add-on allocation.
    BookingAddOnAllocationFinancialStatus:
      title: BookingAddOnAllocationFinancialStatus
      type:
        - string
        - 'null'
      enum:
        - PAID
        - REFUNDED
        - TRANSFERRED_IN
        - null
      description: Read-only financial state stored for a participant add-on allocation.
    ISODate:
      title: ISODate
      type: string
      description: >-
        Represents a date and time in ISO 8601 format as a string.


        The string should follow the format `YYYY-MM-DDTHH:mm:ss.sssZ`, where:

        - `YYYY`: Four-digit year

        - `MM`: Two-digit month (01-12)

        - `DD`: Two-digit day of the month (01-31)

        - `T`: Delimiter indicating the start of the time component

        - `HH`: Two-digit hour in 24-hour format (00-23)

        - `mm`: Two-digit minutes (00-59)

        - `ss.sss`: Seconds with milliseconds (00.000-59.999)

        - `Z`: UTC timezone designator


        **Example:** To represent 11:30 AM on May 8th, 2026, the value would be:
        `"2026-05-08T11:30:00.000Z"`.
      example: '2026-05-08T11:30:00.000Z'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````