> 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/developers/licensing-and-management-apis.md).

# Licensing & Management APIs

Choose between Zentitle2's Licensing API for on-premises apps and its Management API for SaaS integrations, then get the credentials to start.

Zentitle2 offers two APIs depending on where your application runs: a Licensing API for on-premise and SDK-based apps, and a Management API for SaaS and back-office integrations.

### On-premise apps

{% embed url="<https://www.youtube.com/watch?v=sZ72mjnQ6us>" %}

#### NET applications

If you want to implement Zentitle2 in an on-premise app, you can use: - .NET SDK - if .NET is your platform, then the best way is to use our .NET SDK Nuget package. We have prepared it so that it's easy to integrate and provides an API into Zentitle2 functionality. Please refer to the documentation and sample applications we provide to see how to implement the most common scenarios.

→ [Get the SDK](https://docs.nalpeiron.com/zentitle2-docs/developers/the-licensing-client-.net)

#### Other platforms

On other platforms - you can use our **Licensing API** to activate seats and manage features securely.

The Licensing API doesn't require you to store any secrets in the application. To activate your entitlements, it uses a Product ID together with an Activation Code or the end user's own credentials. Your application can also authenticate first, list the entitlements available to the end user, and then activate a seat for the product the user chooses. See [Discover Entitlements Before Activation](https://docs.nalpeiron.com/zentitle2-docs/developers/licensing-and-management-apis/discover-entitlements-before-activation.md).

Using open-source tools, you can use the OpenAPI specification we provide to generate a Client SDK for the most popular platforms.

{% hint style="info" %}
We are also working hard on providing a Windows/Linux/Mac level library that will allow us to generate a system fingerprint, implement secure storage, and various security measures.
{% endhint %}

### SaaS applications and back-office integration

The best choice for Backoffice integrations or SaaS applications is our **Management API.**

It uses the OAuth2 protocol for authentication and allows you to set up and use all features of Zentitle, like creating entitlement, provisioning it, and activating seats.

You can also subscribe to system events via webhooks.

This allows you to react to various events, like entitlement created, entitlement provisioning, notifications about entitlement expiration (30, 7 days before), etc.

Credentials for Management API & Webhooks can be managed from the Zentitle2 UI.

### Zentitle2 has two APIs: a licensing API and a management API.

#### Object IDs

Most objects within Zentitle2 have an ID that can be used with the Management API to reference that object.

IDs follow the convention of having a standard prefix for that object type (e.g. cust\_, prod\_, etc.) followed by a 22-character alphanumeric string.

The entire ID should be provided to the relevant Management API call.

#### Using APIs

The credentials from these APIs are an essential part of the setup and testing phases, and they form part of the key data required to "wire up" your apps to Zentitle2.

→ [Get credentials](https://docs.nalpeiron.com/zentitle2-docs/developers/licensing-and-management-apis/collecting-credentials-for-integration.md)

### Once you have the credentials, start using the APIs

This is the specific API documentation for the Zentitle2 for SaaS and On-Premise applications.

[Management API](https://api.zentitle.io/docs) - The REST API to:

* Manage entitlements within the Zentitle2 platform.
* Activate, query, and manage entitlements from SaaS applications.

[Licensing API](https://license.zentitle.io/docs) - How to activate, query, and manage entitlements from On-Premise applications.


---

# 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/developers/licensing-and-management-apis.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.
