> ## 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 a Stripe checkout session

> 
Check the live Stripe status of a checkout session created via
`POST /partners/checkout-session`, plus the local finance record.

**Use this to verify payment without opening the Stripe URL:**
- `stripe.paymentStatus`: `paid` means the buyer completed payment
- `stripe.status`: `complete` means the session finished
- `fulfilled`: true means tickets were minted (webhook ran)

**Authentication:** Requires valid Partner API Key (Bearer token).
Only sessions belonging to your partner account are visible.
    



## OpenAPI

````yaml /partner-docs/openapi.json get /partners/checkout-sessions/{sessionId}
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/checkout-sessions/{sessionId}:
    get:
      tags:
        - Partner Orders
      summary: Verify a Stripe checkout session
      description: |-

        Check the live Stripe status of a checkout session created via
        `POST /partners/checkout-session`, plus the local finance record.

        **Use this to verify payment without opening the Stripe URL:**
        - `stripe.paymentStatus`: `paid` means the buyer completed payment
        - `stripe.status`: `complete` means the session finished
        - `fulfilled`: true means tickets were minted (webhook ran)

        **Authentication:** Requires valid Partner API Key (Bearer token).
        Only sessions belonging to your partner account are visible.
            
      operationId: PartnerOrdersController_verifyCheckoutSession
      parameters:
        - name: sessionId
          required: true
          in: path
          description: Stripe checkout session ID (returned as sessionId)
          schema:
            example: cs_test_abc123
            type: string
      responses:
        '200':
          description: Session verification result
          content:
            application/json:
              schema:
                type: object
                properties:
                  sessionId:
                    example: cs_test_abc123
                    type: string
                  externalOrderId:
                    type: string
                    example: order_12345
                  stripe:
                    type: object
                    properties:
                      status:
                        type: string
                        example: complete
                      paymentStatus:
                        type: string
                        example: paid
                      amountTotal:
                        type: number
                        example: 31200
                        description: Cents
                      currency:
                        type: string
                        example: usd
                      customerEmail:
                        example: fan@example.com
                        type: string
                  finance:
                    type: object
                    description: Local finance transaction snapshot (null until recorded)
                  ticketsCreated:
                    type: number
                    example: 2
                  fulfilled:
                    type: boolean
                    example: true
        '400':
          description: Invalid session ID or session expired
        '403':
          description: Session not owned by partner
        '404':
          description: Session not found
        '422':
          description: Validation failed or session 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.