> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/api-reference/other-resources/tokens.md).
# SDK Tokens
To securely authenticate users of your frontend app.
**Tokens** enable clients to send personal data to ComplyCube via our SDKs. They are [JWTs](https://jwt.io/).
Each token is confined to one client and **expires after 60 minutes**, so you can safely use them at the front end of your application.
The generated token takes the following form: `{"token": "header.payload.signature"}`.
{% hint style="info" %}
You must generate a new token each time you initialize the ComplyCube SDKs.
{% endhint %}
### The Token object
Attribute
Type
Description
token
string
The client-specific token. It expires after 60 minutes.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.complycube.com/documentation/api-reference/other-resources/tokens.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.