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

# Check partner registration status by email (Public)

> 
Check the status of a partner registration by email address.

**Returns:**
- `exists`: Whether a registration exists
- `status`: Current status (PENDING, ACTIVE, SUSPENDED, REJECTED)
- `partnerId`: Partner ID if exists
- `message`: Human-readable status message

**Status meanings:**
- `PENDING`: Awaiting email verification and/or admin review
- `ACTIVE`: Approved and active, API keys can be generated
- `SUSPENDED`: Account suspended, contact support
- `REJECTED`: Registration rejected, see rejection reason
    



## OpenAPI

````yaml /partner-docs/openapi.json get /partners/register/status/{email}
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/register/status/{email}:
    get:
      tags:
        - Partners
      summary: Check partner registration status by email (Public)
      description: |-

        Check the status of a partner registration by email address.

        **Returns:**
        - `exists`: Whether a registration exists
        - `status`: Current status (PENDING, ACTIVE, SUSPENDED, REJECTED)
        - `partnerId`: Partner ID if exists
        - `message`: Human-readable status message

        **Status meanings:**
        - `PENDING`: Awaiting email verification and/or admin review
        - `ACTIVE`: Approved and active, API keys can be generated
        - `SUSPENDED`: Account suspended, contact support
        - `REJECTED`: Registration rejected, see rejection reason
            
      operationId: PartnersController_checkRegistrationStatus
      parameters:
        - name: email
          required: true
          in: path
          description: Partner contact email to check
          schema:
            type: string
            example: contact@acme.com
      responses:
        '200':
          description: Registration status retrieved
          content:
            application/json:
              schema:
                type: object
                properties:
                  exists:
                    type: boolean
                    example: true
                  status:
                    type: string
                    enum:
                      - PENDING
                      - ACTIVE
                      - SUSPENDED
                      - REJECTED
                    example: PENDING
                  partnerId:
                    type: string
                    example: par_abc123def456
                  message:
                    type: string
                    example: >-
                      Registration submitted. Awaiting email verification and
                      admin review.
        '422':
          description: Validation failed

````

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