> For the complete documentation index, see [llms.txt](https://doc.mantago.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.mantago.cc/mantago-en/documentation-1/client-api.md).

# Client API

### Supported Features

* Bind client accounts
* Unbind client accounts
* Retrieve client profiles
* Retrieve client points
* Retrieve client rewards
* Retrieve client analytics data

***

### Common Use Cases

Typical integration scenarios include:

* E-commerce membership systems
* CRM platforms
* Loyalty programs
* POS systems
* Mobile applications

***

### Authentication Requirements

All Client API requests require:

* Bot ID
* API Token
* Secret Key

Please refer to:

* [How to Get a Token](/mantago-en/faq/how-to-get-a-token.md)
* [Generate Open API Token & Secret Key](/mantago-en/generate-open-api-token-and-secret-key.md)

before making API requests.

***

### Notes

* Each member account should have a unique identifier (`clientId`)
* API requests must include valid authentication credentials
* Expired tokens must be refreshed before use
* Member binding status can be updated dynamically through the API


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.mantago.cc/mantago-en/documentation-1/client-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.