> For the complete documentation index, see [llms.txt](https://docs.payengine.co/developer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payengine.co/developer-docs/getting-started-1/generate-access-tokens.md).

# 3. Generate Access Tokens

### Introduction

In this tutorial, we're going to generate some API tokens that will be needed for the integration process. There are three types of API tokens that can be generated to complete the integration process. Here is a breakdown of each. 

| Token Type | Description                                                                                                                                      |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| Public     | Token that can be placed inside publicly distributed client-side code. This may be a website or a mobile app.                                    |
| Private    | Token that can be used to make calls from your servers to ours. These tokens should never be included anywhere that will be publicly accessible. |

If you don't have a developer role, you may not have access to manage your API in the dashboard. Contact your admin to update your account access level to developer.

Once you created the needed access tokens, you can process the integration options that fit your needs.

### Generate API Keys

Navigate to your API -> Manage Keys section:

**1. Click on the Create API Key**

![](https://2556322805-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MRlN2yYeruyG-6M2wZN%2F-MXzRoNGux9RkJja76Fr%2F-MXzUhAp5LuSnSEAOllW%2FScreen%20Shot%202021-04-11%20at%2012.53.00.png?alt=media\&token=ca9b8855-438b-465b-9e41-e75dcd8437ee)

**2. Provide key details and click `Save`** 

![](https://2556322805-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MRlN2yYeruyG-6M2wZN%2F-MXzRoNGux9RkJja76Fr%2F-MXzUjV8H8fFeJNvmjct%2FScreen%20Shot%202021-04-11%20at%2012.54.12.png?alt=media\&token=d46cb5b7-b1b9-4463-a85b-754c46cd78ed)

### Keeping your keys safe

Your private API key can be used to make any API call on behalf of your account. Ensure it is kept out of any version control system you may be using.

Please note that the private keys are only visible the first time you create them. After that, the Dashboard redacts the API key. If you lose your private key, you can't recover it and must create another one.


---

# 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.payengine.co/developer-docs/getting-started-1/generate-access-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.