> For the complete documentation index, see [llms.txt](https://apidocs.paygateway.paytota.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.paygateway.paytota.com/dashboard/api-tokens.md).

# API Tokens

Each business account can create up-to 2 API Tokens at a given time. The token has two important values; the **api\_key** and the **api\_secret**

### api\_key

Uniquely identifies the merchant it is associated with. Every request must include this key

### api\_secret

This key is also unique to the merchant account. It is required for every authenticated request. In an authenticated request, the **api\_secret** and **api\_key** are mandatory.

### Creating the keys

From the dashboard and from the let navigation of your screen, navigate to the specific business account you want to manage. Once selected, navigate to api tokens page and generate the API tokens.

### Viewing the keys

{% hint style="danger" %}
**NOTE**\
\
Your **api\_key** and the **api\_secret** are displayed once upon generation. However we store the encrypted version of the **api\_secret**. None of us knows your secret so you have to store and use it in the safest way.
{% endhint %}


---

# 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://apidocs.paygateway.paytota.com/dashboard/api-tokens.md?ask=<question>&goal=<user_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.