> ## 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 partner user role

> Change user role between organiser and verifier.



## OpenAPI

````yaml /partner-docs/openapi.json patch /partners/users/{userId}
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/users/{userId}:
    patch:
      tags:
        - Partner Users
      summary: Update partner user role
      description: Change user role between organiser and verifier.
      operationId: PartnerUsersController_updateUserRole
      parameters:
        - name: userId
          required: true
          in: path
          description: User ID (User key)
          schema:
            type: string
            example: user_xyz789
      requestBody:
        required: true
        description: New role
        content:
          application/json:
            schema:
              type: object
              required:
                - role
              properties:
                role:
                  type: string
                  enum:
                    - organiser
                    - verifier
      responses:
        '200':
          description: Role updated
        '400':
          description: User not in partner organization
        '401':
          description: Invalid or missing partner API key
        '403':
          description: User not in partner organization
        '404':
          description: User not found
      security:
        - partner-api-key: []
components:
  securitySchemes:
    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.