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

# Verify partner email token

> Verifies a partner user email using the token sent in the registration verification email.



## OpenAPI

````yaml /partner-docs/openapi.json get /partners/auth/verify
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/auth/verify:
    get:
      tags:
        - Partner Auth
      summary: Verify partner email token
      description: >-
        Verifies a partner user email using the token sent in the registration
        verification email.
      operationId: PartnerAuthController_verifyEmail
      parameters:
        - name: token
          required: true
          in: query
          description: Verification token from email
          schema:
            example: 5e3e7a6872b911e34685d3de274aeba59ad4c6cf417543a0176b13ba4c3398a1
            type: string
      responses:
        '200':
          description: Email verified successfully
        '400':
          description: Invalid or expired token
        '422':
          description: Invalid or expired token

````

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