> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/server-side/integrations/codebase-analyzer/api-tokens.md).

# Platform API Tokens

### Global concept

Platform API tokens are a way to call the Flagship API within your own integrations, in order to automate actions made on the Flagship Platform.

### How to create an API Token?

You can create an API Token in the Flagship platform in the Settings -> Platform Integration section

![1253](https://files.readme.io/12f00b0-menu.png)

An API Token requires a single field to be created:

* **Name**: this field is a plain text field to remember what is the purpose of the Token.

### API Token use cases

Right now, the API Token is used for one purpose only: integrate Flagship with your git solution provider. See [Codebase Analyzer](doc:codebase-analyzer) for more details.

#### Codebase Integration

In that use case, the API Token is passed as an environment variable to the Flagship Codebase Analyzer when running your git solution pipeline.\
See [Codebase Analyzer](doc:codebase-analyzer) for more details.

Any feedback? [We would be really happy to have a quick chat!](mailto:product.feedback@abtasty.com?subject=Flagship%20Custom%20Integration%20Feedback)


---

# 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.abtasty.com/server-side/integrations/codebase-analyzer/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.