> ## Documentation Index
> Fetch the complete documentation index at: https://api-docs.tixyapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Api authorization

# TIXY Connect API Authorization

## Overview

TIXY Connect API employs **Bearer Token** authentication to secure access to both public and private APIs. Tokens are unique to each organizer and are configured via the TIXY organizer panel. Separate tokens are issued for accessing public and private APIs to ensure proper access control.

### Key Features

* **Bearer Token-Based**: Secure and simple token-based authentication.
* **Separate Tokens**: Independent tokens for public and private APIs for granular access control.
* **Configurable via Panel**: Organizers can generate and manage tokens in their TIXY panel.

***

## Token Management

### Generating Tokens

Organizers can generate and manage tokens from their panel on the TIXY platform:

1. Log in to the TIXY platform.
2. Navigate to **API Settings**.
3. Select **Public API Token** or **Private API Token** based on requirements.
4. Click **Generate Token** to create a new token.
5. Save the generated token securely. (It will not be displayed again.)

### Token Types

| **Token Type**    | **Purpose**                                                                 | **Access Scope**              |
| ----------------- | --------------------------------------------------------------------------- | ----------------------------- |
| **Public Token**  | Used for accessing public API endpoints that require minimal authorization. | Limited, low-sensitivity data |
| **Private Token** | Used for accessing private API endpoints that handle sensitive operations.  | Full access to private data   |

***

## Using Tokens in API Requests

Tokens must be included in the `Authorization` header of each API request.

### Example: Public API Authorization

#### Request Header:

```http theme={null}
Authorization: Bearer {PUBLIC_API_TOKEN}
```

### Example: Private API Authorization

#### Request Header:

```http theme={null}
Authorization: Bearer {PRIVATE_API_TOKEN}
```

***

## Best Practices

* Keep tokens confidential and do not share them publicly.
* Regularly rotate tokens to maintain security.
* Use different tokens for different environments (development, staging, production).
* Implement token revocation and regeneration mechanisms.

***

## Troubleshooting

* **Invalid Token**: Ensure the token is correctly copied and matches the one generated in the TIXY panel.
* **Access Denied**: Verify you are using the correct token type (public or private) for the intended API endpoint.

## Setting up

<CardGroup cols={2}>
  <Card title="About TIXY connect" icon="pen-to-square" href="/introduction">
    About TIXY connect
  </Card>

  <Card title="Authorization" icon="users" href="/api-authorization">
    How to authorize api
  </Card>
</CardGroup>

## Avaliable APIs

<CardGroup cols={2}>
  <Card title="Private API" icon="lock" href="/private_API_quickstart">
    Make use of private API
  </Card>

  <Card title="Public API" icon="megaphone" href="/public_API_quickstart">
    Make use of public API
  </Card>
</CardGroup>