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

# Update authenticated partner information

> 
Partially update the authenticated partner's profile information.

**Authentication:** Requires valid Partner API Key in Authorization header (Bearer token).

**Note:** Only fields provided in the request body will be updated. All fields are optional.
    



## OpenAPI

````yaml /partner-docs/openapi.json patch /partners/partners
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/partners:
    patch:
      tags:
        - Partners
      summary: Update authenticated partner information
      description: >-

        Partially update the authenticated partner's profile information.


        **Authentication:** Requires valid Partner API Key in Authorization
        header (Bearer token).


        **Note:** Only fields provided in the request body will be updated. All
        fields are optional.
            
      operationId: PartnersController_updatePartner
      parameters: []
      requestBody:
        required: true
        description: Partner update fields
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpdatePartnerDto'
      responses:
        '200':
          description: Partner updated successfully
          content:
            application/json:
              schema:
                type: object
                properties:
                  partner:
                    type: object
                    properties:
                      partnerId:
                        type: string
                        example: par_abc123def456
                      name:
                        type: string
                        example: Acme Ticketing
                      status:
                        type: string
                        example: ACTIVE
                      website:
                        type: string
                        example: https://acme.com
                        nullable: true
                      contactEmail:
                        type: string
                        example: contact@acme.com
                        nullable: true
                  message:
                    type: string
                    example: Partner updated successfully
        '400':
          description: Invalid input
        '401':
          description: Invalid or missing partner API key
        '404':
          description: Partner not found
        '422':
          description: Validation failed
      security:
        - access-token: []
        - partner-api-key: []
components:
  schemas:
    UpdatePartnerDto:
      type: object
      properties:
        name:
          type: string
          example: Acme Ticketing
          description: Partner name
        website:
          type: string
          example: https://ticketmaster.com
          description: Company website URL
        companyName:
          type: string
          example: Ticketmaster Inc.
          description: Legal company name
        contactEmail:
          type: string
          example: john@acme.com
          description: Contact email
        contactName:
          type: string
          example: John Smith
          description: Contact person name
        country:
          type: string
          example: US
          description: ISO 3166-1 alpha-2 country code
        currency:
          type: string
          example: USD
          description: Default currency (ISO 4217)
        description:
          type: string
          example: Description
          description: Partner description
        status:
          type: string
          example: ACTIVE
          description: Partner status
  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.