> For the complete documentation index, see [llms.txt](https://docs.impossiblecloud.com/partner-portal-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.impossiblecloud.com/partner-portal-help/management-console-guide/using-icmc-as-a-channel-partner/api-keys.md).

# API keys

The "API Keys" page in the Impossible Cloud Management Console (ICMC) is where you can create and manage your API access credentials.

API keys enable programmatic access to ICMC via a [RESTful API](https://api.partner.eu-central-2.impossiblecloud.com/swagger/index.html), which allows you to automate tasks and integrate ICMC features into your applications or workflows. RESTful API stands for Representational State Transfer, a standard software architectural style for creating scalable web services. It enables interaction with ICMC through a set of stateless operations.

When creating a new API Key:

1. Click on '**Create new API Key**' to generate a token.
2. Enter a description and set an expiration date/time for the key.
3. Once created, ensure to copy the key immediately; it's your only chance to do so.
4. The key won't be visible again for security reasons, but you can delete it using the trash bin icon if needed.

Remember, these keys grant access to **ICMC partners features** via API, so handle them securely.


---

# 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.impossiblecloud.com/partner-portal-help/management-console-guide/using-icmc-as-a-channel-partner/api-keys.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.