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

# Refresh expired Stripe Connect onboarding session

> 
Generates a new Stripe Connect onboarding link when the previous one expired.

**Authentication:** Requires valid JWT access token in Authorization header.

**When to use:**
- Partner's onboarding link expired (24 hour expiry)
- Partner needs to retry onboarding after failure

**Authorization:** The authenticated user must be the organizer of the partner
(partner.organizerId must match the user's key). Prevents unauthorized users
from refreshing onboarding for partners they don't manage.

**Response:** HTTP 302 redirect to Stripe onboarding URL.
The partner should be redirected automatically.
    



## OpenAPI

````yaml /partner-docs/openapi.json get /partners/stripe-connect/refresh
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/refresh:
    get:
      tags:
        - Partners
      summary: Refresh expired Stripe Connect onboarding session
      description: >-

        Generates a new Stripe Connect onboarding link when the previous one
        expired.


        **Authentication:** Requires valid JWT access token in Authorization
        header.


        **When to use:**

        - Partner's onboarding link expired (24 hour expiry)

        - Partner needs to retry onboarding after failure


        **Authorization:** The authenticated user must be the organizer of the
        partner

        (partner.organizerId must match the user's key). Prevents unauthorized
        users

        from refreshing onboarding for partners they don't manage.


        **Response:** HTTP 302 redirect to Stripe onboarding URL.

        The partner should be redirected automatically.
            
      operationId: PartnersController_refreshPartnerOnboarding
      parameters:
        - name: partnerId
          required: true
          in: query
          description: Partner ID
          schema:
            type: string
            example: par_abc123def456
      responses:
        '302':
          description: Redirects to Stripe Connect onboarding URL
        '401':
          description: Invalid or missing JWT token
        '403':
          description: User is not the organizer of this partner
        '404':
          description: Partner not found or no Stripe account
      security:
        - access-token: []
components:
  securitySchemes:
    access-token:
      scheme: bearer
      bearerFormat: JWT
      type: http

````

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