Client-side tokens are needed to authenticate with Paddle.js.
You provide a token when initializing Paddle.js. Once initialized, you can take actions like previewing prices, opening checkouts, and running Retain workflows.
Looking to integrate Paddle in your backend? Use API keys instead. API keys must be provisioned through the dashboard.
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 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.