website logo
⌘K
Getting Started
Introduction
Basic Concepts
Opening an Account
Creating & Configuring Products
Integrating SDK and Configuring License Fulfillment
Activate a Key-Based License
Vendor Platform
Issuing New Licenses
License Detail View
Order Detail View
Customer Detail View
Metadata
Analytics
Settings
Product Configuration
Product Features
Product Custom Fields
Product Versioning
License Policies
Product Bundles
License Entitlements
License Types
Activations & Device Transfers
Features
Custom Fields
License Start Date
License Note
Maintenance Period
Trial Licenses
Floating Licenses
License Activation Types
Portals
End-User Portal
Offline Portal
Air-Gapped Portal
License API
License API Authorization
License Activation/Deactivation
License Check
Consumption
Floating
Trial Key
Product Details
Device Variables
Changing Password
Management API
Making API Requests
Management API Authorization
Customer
Product
Order
License
Device
Analytics
SDKs
Tutorials
.NET/C# SDK
.NET/C# Management SDK
C++ SDK
Java SDK
Python SDK
Go SDK
Delphi SDK
Swift/Objective-C SDK
Android SDK
Unity SDK
Errors and Response Codes
Floating Server
API Reference
Deployment
Configuration
Floating Server UI
Securing the Server
Whitelabeling
FAQ
Floating Server Changelog
Integrations
Salesforce
FastSpring
Stripe
Shopify
Common Scenarios
Single Sign On (SSO)
Glossary
General
SDK Glossary
Vendor Platform
Product Configuration Glossary
License Configuration
Postman Collections
Frequently Asked Questions
Changelog
License API changelog
Platform changelog
Docs powered by
Archbee
Glossary
Postman Collections

Management API Collection

4min

Initiate the initial requests within each folder, such as "List Licenses," "List License users," "List orders," "List products," and so forth. These requests establish global variables that can be employed in subsequent requests. The data gathered in these requests pertains to the primary license in the platform's list (or the most recently generated via a request).

Crucial steps to configure for commencing request operations within your organization:

  1. Modify the api_url to https://saas.licensespring.com.
  2. Update apiUrl to https://api.licensespring.com.
  3. Incorporate your managementApiKey, apiKey, and sharedKey from your company's platform settings under the "keys" tab.

These settings are accessible in the LicenseSpring development environment, which must be selected in Postman.

Choose Environment
Choose Environment

Edit Environment
Edit Environment


Manual Data Adjustment

Should there be a desire to manually modify the data (choosing an ID other than the first license), this can be achieved by selecting a specific ID, such as the 35th ID, and designating it as a global variable. This designated variable can subsequently be utilized in the subsequent request.

Setting Globals
Setting Globals


For guidance, you can follow the examples outlined in each request or consult our documentation. You also have the option to modify the name of the {{variable}} within the environment to your desired value.

Alternatively, you can remove the {{variable}} name from the request and directly input the preferred license ID. For example, consider the "Show license" request:

Request URL: https://saas.licensespring.com-api/v1/licenses/1591774919885639

In this URL, the final number "1591774919885639" represents the {{licenseId}}, corresponding to the n-th ID license that you intend to display.

Please note: The initial request within each folder yields a response containing all the necessary data, which can be utilized in other requests within the same folder.

Updated 15 Sep 2023
Did this page help you?
PREVIOUS
Postman Collections
NEXT
License API Collection
Docs powered by
Archbee
TABLE OF CONTENTS
Manual Data Adjustment
Docs powered by
Archbee