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

# Get finance summary for the authenticated partner

> 
Retrieve aggregated financial summary for the authenticated partner.

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

**Metrics returned:**
- `ticketsSold`: Total tickets sold (TICKET_SALE type)
- `grossSales`: Total gross revenue
- `tickifyFees`: Total platform fees
- `refunds`: Total refunded amount
- `adjustments`: Total adjustments
- `netRevenue`: Net revenue (gross - fees - refunds + adjustments)

**Optional filters:**
- `startDate`: Filter from date (ISO 8601)
- `endDate`: Filter to date (ISO 8601)
    



## OpenAPI

````yaml /partner-docs/openapi.json get /partners/finance
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/finance:
    get:
      tags:
        - Partner Finance
      summary: Get finance summary for the authenticated partner
      description: >-

        Retrieve aggregated financial summary for the authenticated partner.


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


        **Metrics returned:**

        - `ticketsSold`: Total tickets sold (TICKET_SALE type)

        - `grossSales`: Total gross revenue

        - `tickifyFees`: Total platform fees

        - `refunds`: Total refunded amount

        - `adjustments`: Total adjustments

        - `netRevenue`: Net revenue (gross - fees - refunds + adjustments)


        **Optional filters:**

        - `startDate`: Filter from date (ISO 8601)

        - `endDate`: Filter to date (ISO 8601)
            
      operationId: PartnerFinanceController_getFinanceSummary
      parameters:
        - name: endDate
          required: false
          in: query
          description: Filter to date (ISO 8601)
          schema:
            type: string
        - name: startDate
          required: false
          in: query
          description: Filter from date (ISO 8601)
          schema:
            type: string
      responses:
        '200':
          description: Financial summary
          content:
            application/json:
              schema:
                type: object
                properties:
                  ticketsSold:
                    type: number
                    example: 1250
                  grossSales:
                    type: number
                    example: 125000
                  tickifyFees:
                    type: number
                    example: 6250
                  refunds:
                    type: number
                    example: 500
                  adjustments:
                    example: 0
                    type: number
                  netRevenue:
                    type: number
                    example: 118250
        '400':
          description: Invalid date format or date range
        '401':
          description: Invalid or missing partner API key
        '422':
          description: Validation failed or partner not found
      security:
        - partner-api-key: []
components:
  securitySchemes:
    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.