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

# Create Access Token

> Generate API access tokens to authenticate your requests to the UniUni Platform API

To use the UniUni Platform API, you need an **access token**. You can generate up to **5 active tokens** at a time from the dashboard.

<Warning>
  Treat access tokens with the same level of security as passwords. Deleting an access token immediately revokes its access.
</Warning>

## Step-by-step

<Steps>
  <Step title="Create a UniUni Platform account">
    Create your free UniUni Platform account.

    | Environment | URL                                                                                      |
    | ----------- | ---------------------------------------------------------------------------------------- |
    | Production  | [ship.uniuni.com/integrations/rest-api](https://ship.uniuni.com/integrations/rest-api)   |
    | Sandbox     | [sandbox.unigo.ca/integrations/rest-api](https://sandbox.unigo.ca/integrations/rest-api) |
  </Step>

  <Step title="Navigate to the REST API integration page">
    Go to **New shipment > Import from integration > REST API** on the UniUni Platform website, or use the direct links below:
  </Step>

  <Step title="Generate a new token">
    Click **Generate New Token**. A Token ID and an Access Token will be displayed — copy the Access Token.
  </Step>

  <Step title="Store the token securely">
    Save the token in a secure location (e.g., environment variables, a secrets manager). You can come back at any time to see your active keys in the Rest API Integration page.
  </Step>
</Steps>

<video autoPlay muted loop controls>
  <source src="https://mintcdn.com/uniexpressinc/ZRFyMCQRxIXQTdkY/videos/create-api-token.mp4?fit=max&auto=format&n=ZRFyMCQRxIXQTdkY&q=85&s=583603a16ac01a84a72954f1d8ccbf07" type="video/mp4" data-path="videos/create-api-token.mp4" />
</video>

## Using your token

Include the token in the `Authorization` header of every API request:

```
Authorization: Bearer <YOUR_ACCESS_TOKEN>
```

## Managing tokens

* You can have up to **5 active tokens** at any time.
* To revoke a token, return to the REST API integration page and **delete** it. Access is revoked immediately.
* Deleting a token cannot be undone — any application using that token will lose access.

<Warning>
  Treat access tokens with the same level of security as passwords. Never share them in public repositories, client-side code, or unencrypted communications.
</Warning>