> For the complete documentation index, see [llms.txt](https://developer.paddle.com/llms.txt).

# Client-side tokens

Client-side tokens hold the details to authenticate Paddle.js in your frontend code.

---

Client-side tokens are needed to authenticate with [Paddle.js](https://developer.paddle.com/paddlejs/overview.md).

You provide a `token` when [initializing Paddle.js](https://developer.paddle.com/paddlejs/include-paddlejs.md). Once initialized, you can take actions like previewing prices, opening checkouts, and running Retain workflows.

{% callout type="note" %}
Looking to integrate Paddle in your backend? Use [API keys](https://developer.paddle.com/api-reference/about/api-keys.md) instead. API keys must be provisioned through the dashboard.
{% /callout %}

You can create as many client-side tokens as you like — useful for when you have multiple Paddle.js integrations and need to differentiate between them.

Client-side token entities hold information like:

- The name and description of the token to identify where and how it's used.
- The token to authenticate with.

### Revoking client-side tokens

You can revoke a client-side token by [updating the token](https://developer.paddle.com/api-reference/client-side-tokens/update-client-token.md) with a `status` of `revoked`. This prevents the token from being used to authenticate Paddle.js. Before you revoke the token, confirm it's no longer being used in production to prevent disruption.