> ## 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 access token for authenticated partner

> Exchange partner credentials for a JWT access token.

Use this endpoint to obtain an access_token that can be used with all partner endpoints. The token is signed with the JWT secret and expires in 24 hours.



## OpenAPI

````yaml /partner-docs/openapi.json post /partners/auth/token
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/auth/token:
    post:
      tags:
        - Partner Auth
      summary: Get access token for authenticated partner
      description: >-
        Exchange partner credentials for a JWT access token.


        Use this endpoint to obtain an access_token that can be used with all
        partner endpoints. The token is signed with the JWT secret and expires
        in 24 hours.
      operationId: PartnerAuthController_getAccessToken
      parameters: []
      requestBody:
        required: true
        description: Login credentials
        content:
          application/json:
            schema:
              type: object
              required:
                - email
                - password
              properties:
                email:
                  type: string
                  format: email
                password:
                  type: string
      responses:
        '200':
          description: Access token retrieved successfully
          content:
            application/json:
              schema:
                type: object
                properties:
                  access_token:
                    type: string
                    description: JWT access token
                  user:
                    type: object
                    description: Partner user profile
        '401':
          description: Invalid credentials
        '422':
          description: Validation failed or token generation failed

````

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