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

# Get custom questions

> Returns the custom questions configured for an experience. Answers are submitted inside the [booking call](/api-reference/carts-and-checkout/create-booking), not saved separately.



## OpenAPI

````yaml get /v1/brands/{brandId}/experiences/{experienceId}/custom-questions
openapi: 3.0.0
info:
  title: Way Partner API
  description: >-
    REST API for Way partners: list experiences, check availability, run
    checkout, and manage bookings.
  version: '1.0'
servers:
  - url: https://api.letsway.com
    description: Production.
  - url: https://api.staging.letsway.com
    description: Staging.
security: []
tags:
  - name: Listings
    description: 'Retrieve the listings a brand offers: experiences, events, and resources.'
  - name: Availability
    description: Dates, sessions, and price tiers for scheduling a booking.
  - name: Carts & Checkout
    description: >-
      Payment intents and booking creation. The cart ID is a client-generated
      UUID; there is no create-cart endpoint.
  - name: Bookings
    description: Retrieve, cancel, and reschedule bookings.
  - name: Experiences
    description: Experience details, settings, custom questions, reviews, and hosts.
  - name: Brand Configuration
    description: Brand settings, taxonomy, terms, and promotion code validation.
  - name: Waitlists
    description: Waitlists for sold-out sessions and invitation handling.
  - name: Integrations
    description: Configured integrations, analytics, and room-charge validation.
  - name: Organizations
    description: Organization-level access across brands.
paths:
  /v1/brands/{brandId}/experiences/{experienceId}/custom-questions:
    get:
      tags:
        - Experiences
      summary: Get custom questions
      description: >-
        Returns the custom questions configured for an experience. Answers are
        submitted inside the [booking
        call](/api-reference/carts-and-checkout/create-booking), not saved
        separately.
      operationId: CustomQuestionPublicController_getAll
      parameters:
        - $ref: '#/components/parameters/brandIdPath_51'
        - $ref: '#/components/parameters/experienceIdPath_52'
      responses:
        '200':
          description: Get custom questions.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ItemsCustomQuestionDto'
              example:
                items: []
      security:
        - Brand-API-Key: []
        - Organization-API-Key: []
components:
  parameters:
    brandIdPath_51:
      name: brandId
      in: path
      schema:
        type: string
      required: true
      description: >-
        The brand's ID - must match the brand your API key identifies (or the
        Way-Brand-Id header when one is sent).
    experienceIdPath_52:
      name: experienceId
      in: path
      schema:
        type: string
      required: true
      description: Only results for this experience.
      example: c99f70ee-1c0e-4534-a31a-96d5d966cc4b
  schemas:
    ItemsCustomQuestionDto:
      type: object
      properties:
        items:
          description: List of items.
          type: array
          items:
            $ref: '#/components/schemas/CustomQuestionResponseDto'
      required:
        - items
    CustomQuestionResponseDto:
      type: object
      properties:
        id:
          type: string
          description: Unique identifier of the question.
          example: qst-123
        prompt:
          type: string
          description: The question prompt.
          example: What is your favorite color?
        fieldType:
          type: string
          description: Field type of the question.
          enum:
            - input
            - textarea
            - multiple_select
            - single_select
            - terms_and_conditions
          example: single_select
        options:
          description: Available options for selection.
          type: array
          items:
            $ref: '#/components/schemas/OptionDto'
        termsAndConditions:
          description: Terms and conditions associated with the question.
          allOf:
            - $ref: '#/components/schemas/TermAndConditionDto'
        config:
          type: object
          description: Configuration settings for the question.
          example:
            maxLength: 100
      required:
        - id
        - prompt
        - fieldType
        - config
    OptionDto:
      type: object
      properties:
        key:
          type: string
          description: The key of the option.
          example: color
        value:
          type: string
          description: The value of the option.
          example: blue
      required:
        - key
        - value
    TermAndConditionDto:
      type: object
      properties:
        label:
          type: string
          description: The label for the term and condition.
          example: Terms of Service
        mediaId:
          type: string
          description: Media ID associated with the terms.
          example: 550e8400-e29b-41d4-a716-446655440000
        mediaURL:
          type: string
          description: URL of the media file.
          example: https://example.com/media.pdf
        isOverrided:
          type: boolean
          description: Indicates if the term is overridden.
          example: true
      required:
        - label
        - mediaId
        - mediaURL
        - isOverrided
  securitySchemes:
    Brand-API-Key:
      type: http
      scheme: bearer
      description: >-
        Your brand's secret API key, e.g. `Bearer
        way_sk_live_bhEqcn0i1fRoUEHBPjJkQA`. Older `Way-Brand-Id` +
        `Way-Secret-Key` credentials still work: see [Legacy
        authentication](/legacy-authentication).
    Organization-API-Key:
      type: http
      scheme: bearer
      description: >-
        Your organization's secret API key, e.g. `Bearer
        way_sk_live_ohEqcn0i1fRoUEHBPjJkQA`. Older `Way-Organization-Id` +
        `Way-Secret-Key` credentials still work: see [Legacy
        authentication](/legacy-authentication).

````