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

# List add-on services

> List the add-on services of a scheduling link, in display order.

<Info>Replace `{your-subdomain}` with your workspace’s subdomain. <br /> Learn how to find your subdomain in [Workspace subdomain](/api/workspace-subdomain).</Info>


## OpenAPI

````yaml bundled/add-on-services.yaml GET /meetings/{meeting_sid}/add-on-services
openapi: 3.0.3
info:
  title: NeetoCal Add-on Services APIs
  version: 2.0.0
servers:
  - description: NeetoCal APIs
    url: https://{your-subdomain}.neetocal.com/api/external/v2
    variables:
      your-subdomain:
        default: spinkart
        description: >-
          Replace **spinkart** with your [workspace's
          subdomain](/api/workspace-subdomain).
security: []
tags:
  - name: Add-on Services
    description: >-
      APIs to manage the add-on services people can choose when booking a
      scheduling link.
paths:
  /meetings/{meeting_sid}/add-on-services:
    get:
      tags:
        - Add-on Services
      summary: List add-on services
      description: List the add-on services of a scheduling link, in display order.
      parameters:
        - $ref: '#/components/parameters/api_key_header'
        - $ref: '#/components/parameters/meeting_sid'
      responses:
        '200':
          description: OK - Request succeeded
          content:
            application/json:
              schema:
                type: object
                properties:
                  add_on_services:
                    type: array
                    items:
                      $ref: '#/components/schemas/add_on_service'
components:
  parameters:
    api_key_header:
      in: header
      name: X-Api-Key
      description: >-
        Use the X-Api-Key header to provide your workspace API key. Refer to
        [Authentication](/api/authentication) for more information.
      required: true
      schema:
        type: string
    meeting_sid:
      in: path
      name: meeting_sid
      description: >
        The unique identifier (SID) of the scheduling link you want to use. You
        can get `sid` in different ways. Visit the scheduling link page and then
        click on "Settings" > "Show SID". That will give you `sid`. You can also
        get this from the response of the [List scheduling
        links](/api/scheduling-links/list) endpoint, where it appears as the
        `sid` property for each scheduling link in the response.
      required: true
      schema:
        type: string
        example: vj5pgkh
  schemas:
    add_on_service:
      type: object
      properties:
        id:
          type: string
          description: Unique identifier for the add-on service.
          example: 77150ec6-d4f0-4665-98f0-34bda69f7b3a
        name:
          type: string
          description: Name of the add-on service shown to the person booking.
          example: Sauna
        description:
          type: string
          nullable: true
          description: Description of the add-on service.
          example: 20 minutes in the sauna
        duration:
          type: integer
          minimum: 0
          maximum: 1440
          description: Minutes the add-on service adds to the booking.
          example: 30
        position:
          type: integer
          description: Display order of the add-on service, starting at 1.
          example: 1
        price:
          type: string
          nullable: true
          description: >-
            Price of the add-on service in the major unit of `currency`,
            returned as a decimal string to keep its exact value (the request
            takes it as a number). `null` when the add-on service is free.
          example: '25.5'
        currency:
          type: string
          nullable: true
          description: >-
            Currency of `price`, taken from the scheduling link's fee. `null`
            when the add-on service is free.
          example: usd
        payment_provider:
          type: string
          nullable: true
          description: >-
            Payment provider used to collect `price`, taken from the scheduling
            link's fee. `null` when the add-on service is free.
          example: stripe
        created_at:
          type: string
          format: date-time
          description: Timestamp when the add-on service was created.
          example: '2026-10-06T18:26:08.033Z'
        updated_at:
          type: string
          format: date-time
          description: Timestamp when the add-on service was last updated.
          example: '2026-10-06T18:26:08.264Z'

````

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