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

# Transfer ticket to a new recipient

> 
Transfer an existing ticket from its current owner to a new recipient email address.

**Workflow:**
1. Validates that the ticket belongs to the partner and is active (not USED or REFUNDED).
2. Initiates the transfer sequence within Tickify.
3. Triggers the `ticket.transferred` webhook to notify the partner application.
    



## OpenAPI

````yaml /partner-docs/openapi.json post /partners/tickets/{ticketId}/transfer
openapi: 3.0.0
info:
  title: Tickify Partner API
  description: >2-

        API documentation for the Tickify Partner Platform.

        Getting Started:
    1. Register as a partner and wait for approval from the Tickify team.
        2. Once approved, request an API key from the Tickify team. A Tickify admin will generate and securely share your API key with you.
        3. Use your API key to authenticate partner API requests.
        4. Generate an access token using the /partner/auth/token endpoint in the Auth documentation.
        5. Use the access token for authenticated requests where required.

        **API Keys:**
    - Test keys use the 

    `tk_test_` prefix. These keys work in sandbox mode and never charge real
    payment methods.

    - Live keys use the 

    `tk_live_` prefix. These keys process real payments and require completed
    Stripe Connect onboarding.

    - Both key types follow the same API behavior — only the payment environment
    differs.

    - To test checkout flows without real charges, use 

    `tk_test_` keys and include test card numbers in your Stripe integration.
        
  version: '1.0'
  contact: {}
servers:
  - url: http://localhost:3000
    description: Local Development
  - url: https://api-staging.tickify.io
    description: Staging
  - url: https://api.tickify.io
    description: Production
security: []
tags: []
paths:
  /partners/tickets/{ticketId}/transfer:
    post:
      tags:
        - Partner Tickets
      summary: Transfer ticket to a new recipient
      description: >-

        Transfer an existing ticket from its current owner to a new recipient
        email address.


        **Workflow:**

        1. Validates that the ticket belongs to the partner and is active (not
        USED or REFUNDED).

        2. Initiates the transfer sequence within Tickify.

        3. Triggers the `ticket.transferred` webhook to notify the partner
        application.
            
      operationId: PartnerTicketsController_transferTicket
      parameters:
        - name: ticketId
          required: true
          in: path
          description: Unique ticket ID (MongoDB _id) to transfer
          schema:
            type: string
            example: 64a1b2c3d4e5f6789012345
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                ticketId:
                  type: string
                  example: 64a1b2c3d4e5f6789012345
                recipientEmail:
                  type: string
                  example: friend@example.com
                recipientName:
                  type: string
                  example: Jane Doe
                message:
                  type: string
                  example: Enjoy the show!
      responses:
        '200':
          description: Ticket transfer initiated successfully
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: true
                  message:
                    type: string
                    example: Ticket transfer initiated
        '400':
          description: Ticket cannot be transferred (e.g., already used or refunded)
        '401':
          description: Invalid or missing partner API key
        '403':
          description: Ticket not owned by partner events
        '404':
          description: Ticket not found
        '422':
          description: Validation failed or ticket not found
      security:
        - access-token: []
        - partner-api-key: []
components:
  securitySchemes:
    access-token:
      scheme: bearer
      bearerFormat: JWT
      type: http
    partner-api-key:
      type: apiKey
      in: header
      name: x-partner-key
      description: Partner API Key (tk_live_... or tk_test_...)

````

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