> 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
Find your Tenant ID, Management API endpoint URL, and OAuth URL on the API Credentials page to connect your apps to the Nalpeiron Growth Platform.
The "API Credentials" section is located under the "**Administration**" > "**API Credentials**" on the top **Administration** menu.
The Nalpeiron Growth Platform has two APIs: a **licensing API** and a **management API.**
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 %}
## Management API access levels
When you create a Management API client, choose its **Access level**:
* **Full access**, selected by default, allows the client to read and modify Management API resources, including API credentials.
* **Read-only** allows the client to read products, customers, resellers, users, and entitlements. It cannot create, modify, or delete resources, or list or manage API credentials.
Choose **Read-only** for integrations that only need to retrieve data, such as reporting tools.
### Create read-only credentials
1. Open **Administration** > **API Credentials** and go to **Management API**.
2. In **Management API Clients**, click **Add API Client**.
3. Enter a **Client ID**.
4. Set **Access level** to **Read-only** and submit the form.
5. Copy and securely save the **Client ID** and **Client secret** before closing the panel.
Use the Client ID and Client secret with the OAuth URL shown on this page to authenticate, just as you would with full-access credentials. Requests outside the client's permissions return **403 Forbidden**.
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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.nalpeiron.com/zentitle2-docs/ui-administration/api-credentials.md?ask=&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.
