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

# Open a Leap support case

> Opens a partner_support_case in the Leap Inbox, or returns the case already open for this referenceId. The partner identifies the person only by referenceId. That person may not exist in RaaS yet, so the call does not require a userId and does not fail when none is found. The platform stores the summary and the console URL. It does not store the conversation.



## OpenAPI

````yaml /raas-widgets/openapi.json post /partner/support-cases
openapi: 3.0.0
info:
  title: RaaS Widgets Partner API
  description: >
    REST API for RaaS Widgets partner integrations. Create magic links for
    embeddable flows, manage end users, track transfer operations, handle CIP
    verification, and configure webhooks for real-time event notifications.


    This specification covers the **Partner-accessible API** only (`X-API-Key`
    against `/partner/*`). Widget and Superadmin APIs are out of scope.


    ## Authentication


    All endpoints require an API key passed in the `X-API-Key` header. Use
    `raas_sandbox_*` keys for the sandbox environment and `raas_live_*` keys for
    production.


    ## Environments


    | Environment | Base URL |

    |---|---|

    | Sandbox | `https://api.sandbox.raas-widgets.leapfinancial.com` |
  version: 3.16.2
  contact: {}
servers:
  - url: https://api.sandbox.raas-widgets.leapfinancial.com
    description: Sandbox
security: []
tags:
  - name: Partner - Magic Links
    description: Create, list, and manage magic links for flows
  - name: Partner - Flows
    description: List enabled flows and the full flow catalog
  - name: Partner - Users
    description: View and manage end users associated with your partner account
  - name: Partner - Operations
    description: Track money transfer operations and their statuses
  - name: Partner - Requests
    description: List and inspect money-request records
  - name: Partner - Deferred Payouts
    description: List, inspect, and cancel deferred payout remittances
  - name: Partner - CIP
    description: Customer Identification Program (CIP) verification management
  - name: Partner - Data Requests
    description: Fulfill data requests for additional user information
  - name: Partner - Settings
    description: Configure partner-level settings (redirect URLs, logo, etc.)
  - name: Partner - Webhooks
    description: Configure webhook endpoints and inspect delivery history
  - name: Partner - Pricing
    description: >-
      Indicative pre-quote summaries (best / worst / averages) for partner
      integrations
paths:
  /partner/support-cases:
    post:
      tags:
        - Partner - Support cases
      summary: Open a Leap support case
      description: >-
        Opens a partner_support_case in the Leap Inbox, or returns the case
        already open for this referenceId. The partner identifies the person
        only by referenceId. That person may not exist in RaaS yet, so the call
        does not require a userId and does not fail when none is found. The
        platform stores the summary and the console URL. It does not store the
        conversation.
      operationId: SupportCasesController_open
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateSupportCaseDto'
      responses:
        '200':
          description: Case opened or already open
      security:
        - api-key: []
components:
  schemas:
    CreateSupportCaseDto:
      type: object
      properties:
        referenceId:
          type: string
          description: >-
            End user id in the partner system (for Lola, wa:<E.164>). This is
            the only identity the partner sends. A RaaS userId is not required:
            the person may not have onboarded yet, so no User row exists. The
            case is stored on this referenceId. If a User with the same
            partnerId and referenceId already exists, the inbox item also gets
            that userId.
          example: wa:+5215512345678
        subtype:
          type: string
          enum:
            - general
            - cancellation_intent
            - operation_issue
        summary:
          type: string
          description: >-
            What the user needs, followed by a recent transcript the agent can
            read before opening the console
          maxLength: 4000
        severity:
          type: string
          enum:
            - low
            - medium
            - high
            - critical
          description: >-
            Inbox priority. When omitted, cancellation_intent is high and every
            other subtype is medium.
        externalUrl:
          type: string
          description: >-
            HTTPS URL of the partner console. http is accepted only for
            localhost.
          example: https://lola.example.com/support/console
        externalRef:
          type: string
          description: Partner-side id for this conversation, stored as-is
        channel:
          type: string
          description: Descriptive channel label. The platform does not branch on it.
          example: whatsapp
        operationId:
          type: string
          description: Operation this case is about. Must belong to the caller.
      required:
        - referenceId
        - subtype
        - summary
        - externalUrl
  securitySchemes:
    api-key:
      type: apiKey
      in: header
      name: X-API-Key
      description: >-
        Your partner API key. Use `raas_sandbox_*` keys for the sandbox
        environment and `raas_live_*` keys for production.

````

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