> ## 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 Stripe Connect onboarding status for authenticated partner

> 
Checks if the authenticated partner has completed Stripe Connect onboarding (KYC).

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

**When to use:**
- After partner returns from onboarding URL
- Periodically to check onboarding status
- Before attempting to create checkout sessions for the partner

**Response statuses:**
- `verified`: Partner completed KYC, `charges_enabled: true`, payouts can be sent
- `pending`: KYC incomplete, check `currently_due` for missing requirements

**Currently due requirements may include:**
- `business_profile.url`: Business website
- `company.address`: Company address
- `company.tax_id`: Tax ID
- `individual.email`: Individual email
- `individual.phone`: Phone number
- `external_account`: Bank account for payouts
    



## OpenAPI

````yaml /partner-docs/openapi.json get /partners/stripe-connect/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/stripe-connect/verify:
    get:
      tags:
        - Partners
      summary: Verify Stripe Connect onboarding status for authenticated partner
      description: >-

        Checks if the authenticated partner has completed Stripe Connect
        onboarding (KYC).


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


        **When to use:**

        - After partner returns from onboarding URL

        - Periodically to check onboarding status

        - Before attempting to create checkout sessions for the partner


        **Response statuses:**

        - `verified`: Partner completed KYC, `charges_enabled: true`, payouts
        can be sent

        - `pending`: KYC incomplete, check `currently_due` for missing
        requirements


        **Currently due requirements may include:**

        - `business_profile.url`: Business website

        - `company.address`: Company address

        - `company.tax_id`: Tax ID

        - `individual.email`: Individual email

        - `individual.phone`: Phone number

        - `external_account`: Bank account for payouts
            
      operationId: PartnersController_verifyPartnerStripe
      parameters: []
      responses:
        '200':
          description: Onboarding status retrieved
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                      - verified
                      - pending
                    example: verified
                  details_submitted:
                    type: boolean
                    example: true
                  currently_due:
                    type: array
                    items:
                      type: string
                    example:
                      - business_profile.url
                      - external_account
                    description: Missing KYC requirements (only when status=pending)
        '401':
          description: Invalid or missing partner API key
        '404':
          description: Partner not found or no Stripe account connected
        '422':
          description: Validation failed or partner 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.