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.
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.
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.
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.
Open Postman
Go to Environments → Import → select LS Environment.json
Go to Collections → Import and import:
License API.postman_collection.json
License API – OAuth.postman_collection.json
LicenseSpring Management API.postman_collection.json
Select the LS Environment from Postman’s environment dropdown
Run List requests to populate variables
Use the collections normally — all requests will use environment variables dynamically
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.
Last updated
Was this helpful?
Was this helpful?