> ## 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.

# Create a CIP verification ticket

> Creates a new CIP (Customer Identification Program) verification ticket. Returns a widget URL where the end user can complete identity verification. The link must have sufficient user data (check readiness first) and must not be revoked.



## OpenAPI

````yaml /m2m/openapi.json post /partner/cip/tickets
openapi: 3.0.0
info:
  title: M2M Partner API
  description: >
    REST API for M2M partner integrations. Create magic links to enable
    cross-border money transfers, manage end users, track transfer operations,
    handle CIP verification, and configure webhooks for real-time event
    notifications.


    ## Authentication


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


    ## Environments


    | Environment | Base URL |

    |---|---|

    | Sandbox | `https://m2m-backend-qa.up.railway.app` |
  version: 0.5.3
  contact: {}
servers:
  - url: https://m2m-backend-qa.up.railway.app
    description: Sandbox
security: []
tags:
  - name: Partner - Magic Links
    description: Create, list, and manage magic links for money transfers
  - 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 - 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, etc.)
  - name: Partner - Webhooks
    description: Configure webhook endpoints and inspect delivery history
paths:
  /partner/cip/tickets:
    post:
      tags:
        - Partner - CIP
      summary: Create a CIP verification ticket
      description: >-
        Creates a new CIP (Customer Identification Program) verification ticket.
        Returns a widget URL where the end user can complete identity
        verification. The link must have sufficient user data (check readiness
        first) and must not be revoked.
      operationId: CipController_createTicket
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateCipTicketDto'
      responses:
        '201':
          description: CIP ticket created successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CipTicketResponseDto'
        '401':
          description: Unauthorized — invalid or missing API key / bearer token
        '403':
          description: Link is revoked and cannot be used for CIP verification
        '404':
          description: Magic link not found
      security:
        - bearer: []
        - api-key: []
components:
  schemas:
    CreateCipTicketDto:
      type: object
      properties:
        linkId:
          type: string
          description: The link ID to create a CIP ticket for
          example: link_kapital_a1b2c3d4e5f6
      required:
        - linkId
    CipTicketResponseDto:
      type: object
      properties:
        success:
          type: boolean
          example: true
        data:
          $ref: '#/components/schemas/CipTicketDataDto'
      required:
        - success
        - data
    CipTicketDataDto:
      type: object
      properties:
        ticketId:
          type: string
          description: Kentucky CIP ticket ID
          example: 53a18402-d3ef-4140-a81b-bd7d50487de4
        widgetUrl:
          type: string
          description: URL for the CIP widget where user completes verification
          example: >-
            https://lola-kentucky-front-dev.up.railway.app/53a18402-d3ef-4140-a81b-bd7d50487de4/raas?ph=1
        referenceId:
          type: string
          description: Reference ID from the link for correlation
          example: '526621057979'
      required:
        - ticketId
        - widgetUrl
        - referenceId
  securitySchemes:
    api-key:
      type: apiKey
      in: header
      name: X-API-Key
      description: Your partner API key. Use `m2m_test_*` keys for the sandbox environment.

````