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

# List your brand's qualification question library

> Returns your brand's reusable screening questions — the library you fork onto offerings.



## OpenAPI

````yaml /openapi/public-openapi.json get /v1/account/question-library/questions
openapi: 3.1.0
info:
  title: Purple API
  version: 0.0.0
servers:
  - url: https://api.dev.purplelabelmd.com
security: []
tags:
  - description: Sign a patient in and out and manage the browser session.
    name: Sessions & authentication
  - description: Run the server-driven intake questionnaire question by question.
    name: Intake
  - description: Address autocomplete for the intake flow.
    name: Addresses
  - description: Read the public status of a patient's enrollment.
    name: Enrollment
  - description: Track a client's onboarding progress.
    name: Onboarding
  - description: Read back the platform configuration stored for your brand.
    name: Brand configuration
  - description: Enable offerings for your brand and set their display copy.
    name: Offering configuration
  - description: Start and track payments for an order.
    name: Payments
  - description: Subscribe to platform events and manage delivery endpoints.
    name: Webhooks
paths:
  /v1/account/question-library/questions:
    get:
      tags:
        - Offering configuration
      summary: List your brand's qualification question library
      description: >-
        Returns your brand's reusable screening questions — the library you fork
        onto offerings.
      operationId: listQualificationLibrary
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/QualificationLibraryResponse'
          description: the brand's question library
      security:
        - apiKey: []
components:
  schemas:
    QualificationLibraryResponse:
      description: your brand's question library under `data`, in creation order
      properties:
        data:
          items:
            $ref: '#/components/schemas/QualificationOverlayQuestion'
          type: array
      required:
        - data
      type: object
    QualificationOverlayQuestion:
      description: >-
        A client-authored screening question — a library definition or an
        offering-local copy. It binds a fact by its stable code (the code must
        resolve in your authoring fact catalog) and a display control, and
        carries your own wording. Copy and option labels are yours to author.
      properties:
        control:
          enum:
            - single_select_cards
            - multi_select_cards
            - scale
            - number
            - number_pair
            - date
            - text
            - long_text
            - file_capture
            - address
            - phone
            - email
            - search_select
          type: string
        copy:
          additionalProperties:
            type: string
          description: your display copy (the question prompt rides the `prompt` slot)
          type: object
        fact:
          description: >-
            the stable code of the catalog fact this question collects (must
            resolve)
          type: string
        id:
          type: string
        option_labels:
          additionalProperties:
            type: string
          description: >-
            your per-option labels, keyed by option code (labels never bind
            logic)
          type: object
        options:
          description: >-
            stable option codes offered as answers — a subset of the bound
            fact's own codes
          items:
            type: string
          type: array
        required:
          type: boolean
        when:
          allOf:
            - $ref: '#/components/schemas/QualificationCondition'
          description: >-
            an optional condition — show this question only when an earlier
            screening answer calls for it (for example, ask "how long have you
            used one?" only after "have you used one?" is yes). A condition may
            use only facts collected by questions shown EARLIER in this
            offering; never a medical-intake answer or another brand's fact.
            When the condition is not met the question is skipped; with no
            condition the question is always shown. Accepted and validated at
            authoring now; conditional serving activates in a coming release
            (see the changelog).
      required:
        - id
        - fact
        - control
      type: object
    QualificationCondition:
      additionalProperties: true
      description: >-
        A condition on a screening question, built from your own earlier
        screening answers. It compares an earlier answer to a value, or combines
        such comparisons, in the same rule language the platform uses to serve
        questions. The question is shown only when the condition holds.
      properties:
        kind:
          description: >-
            the kind of condition node (comparison, presence check, boolean
            combination, or if/else)
          enum:
            - compare
            - 'null'
            - bool
            - cond
          type: string
      required:
        - kind
      type: object
  securitySchemes:
    apiKey:
      description: 'Per-client API key (M2M). Presented as `Authorization: Bearer <key>`.'
      scheme: bearer
      type: http

````