> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/ui-administration/api-credentials.md).

# API Credentials

The "API Credentials" section is located under the "**Administration**" > "**API Credentials**" on the top **Administration** menu.

<figure><img src="/files/YEPCcCNsADPG36lzsqo6" alt=""><figcaption></figcaption></figure>

The Nalpeiron Growth Platform has two APIs: a **licensing API** and a **management API.**

<figure><img src="/files/ZZv7C4ujLJUzpg8SaaS5" alt=""><figcaption></figcaption></figure>

The management API credentials are essential for the setup and testing phases and form part of the critical data required to "wire up" your apps to the Nalpeiron Growth Platform.

In addition to these details, for the licensing API, you will also need a **Product ID** key from the "products" you add to the Nalpeiron Growth Platform and an **Activation Code** to test with, depending on your use case.

{% hint style="info" %}
Please ensure you create the required keys and codes, keep them secure, and have them ready for use in your application before you start testing.
{% endhint %}

{% hint style="warning" %}
Note that at this time, all API client credentials generated have full permissions.
{% endhint %}

This page also shows your Tenant ID (needed for calls to the Management API), the URL of your Management API endpoint, and the OAuth URL to use.

Now [go to the SDK and API documentation](/zentitle2-docs/developers/licensing-and-management-apis.md) to learn how to create and use these credentials.


---

# 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://docs.nalpeiron.com/zentitle2-docs/ui-administration/api-credentials.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.
