> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/common-scenarios/glossary/postman-collections.md).

# Postman Collections

### Management API Collection

The **Management API Postman Collection** provides a complete and structured set of requests for interacting with the LicenseSpring Management API.\
It enables developers to manage customers, products, licenses, devices, accounts, features, labels, analytics, and other platform resources.

The collection is fully integrated with the shared environment file, allowing automatic population of resource IDs for fast and efficient testing.

{% file src="/files/YFMehvlrNpWTJAI3tUmO" %}

### License API Collection

The **License API Postman Collection** is a valuable resource designed to empower businesses in efficiently managing their software licenses; it includes all essential endpoints for working with software licensing.

This collection supports **API Key** and **Shared Key** authentication and uses environment variables for product codes, license keys, and hardware IDs, making setup quick and flexible.

{% file src="/files/d4V5SczR1Gn2aF5Wxowh" %}

The **License API – OAuth Postman Collection** provides the same licensing functionality as the standard License API collection, but using **OAuth authentication**.

The collection includes:

* Token generation flow using client\_id and client\_secret
* Automatic insertion of access tokens into all subsequent requests
* Fully aligned endpoints with the non-OAuth License API

This makes it suitable for secure server-side integrations and enterprise setups where OAuth is required.

{% file src="/files/4Lu95bPnDFN1yq2s3dGX" %}

### User Environment Collection

The LS Environment Postman Collection is a valuable asset aimed at streamlining the management of user environments.

This collection provides a curated set of API requests and endpoints, simplifying the interaction with user environment configurations.

{% file src="/files/7jOnzCfmRRef2Br26fei" %}

### How to Import and Use

{% stepper %}
{% step %}
Open Postman
{% endstep %}

{% step %}
Go to Environments → Import → select LS Environment.json
{% endstep %}

{% step %}
Go to Collections → Import and import:

* License API.postman\_collection.json
* License API – OAuth.postman\_collection.json
* LicenseSpring Management API.postman\_collection.json
  {% endstep %}

{% step %}
Select the LS Environment from Postman’s environment dropdown
{% endstep %}

{% step %}
Run List requests to populate variables
{% endstep %}

{% step %}
Use the collections normally — all requests will use environment variables dynamically
{% endstep %}
{% endstepper %}

### Notes

* The setup is fully customizable; users may modify or extend variables and requests.
* All required variables for License and Management APIs are available through the LicenseSpring platform UI.
* Management API POST requests include example payloads based on official API documentation.
* License API requests depend on: apiKey and sharedKey or if using OAuth client\_id and client\_secret; and requests mostly require: default\_product\_code, default\_license\_key and default\_hardware\_id. Once set, headers and bodies are generated automatically.
* Environment values must not contain trailing spaces or hidden characters. Such issues commonly cause URL errors, authentication failures (401), or unexpected 400/404 responses.
* OAuth-specific folders in the Management API require populated IDs (e.g., license\_id, customer\_id). These are filled automatically when List requests are run, or they can be set manually.


---

# 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.licensespring.com/common-scenarios/glossary/postman-collections.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.