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

# Assign verifiers to an event

> 
Assign one or more verifiers to an event.

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

**Verifiers** can scan tickets at the venue using the Tickify verifier app.
They receive scan notifications and can validate ticket authenticity.

**Body:** `verifierIds` - Array of user keys (format: `user_xxx`)
    



## OpenAPI

````yaml /partner-docs/openapi.json post /partners/events/{eventId}/verifiers
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/events/{eventId}/verifiers:
    post:
      tags:
        - Partner Verifiers
      summary: Assign verifiers to an event
      description: >-

        Assign one or more verifiers to an event.


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


        **Verifiers** can scan tickets at the venue using the Tickify verifier
        app.

        They receive scan notifications and can validate ticket authenticity.


        **Body:** `verifierIds` - Array of user keys (format: `user_xxx`)
            
      operationId: PartnerVerifiersController_assignVerifiers
      parameters:
        - name: eventId
          required: true
          in: path
          description: Event ID
          schema:
            example: evt_xyz789
            type: string
      requestBody:
        required: true
        description: Array of verifier user IDs
        content:
          application/json:
            schema:
              type: object
              required:
                - verifierIds
              properties:
                verifierIds:
                  type: array
                  items:
                    type: string
                    example: user_abc123
                  minItems: 1
      responses:
        '200':
          description: Verifiers assigned
        '400':
          description: Invalid verifier IDs
        '401':
          description: Invalid or missing partner API key
        '403':
          description: Event not owned by partner
        '404':
          description: Event not found
        '422':
          description: Validation failed or event 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.