NetLicensing API Documentation

This is the complete API documentation for connecting to the NetLicensing API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet NetLicensing: NetLicensing is a license management and software monetization platform for managing products, licensees, licenses, tokens, transactions, bundles, and related licensing resources through a REST API. Keep reading to get started.

Quickstart

Before you run your first NetLicensing request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one NetLicensing connection — create or choose one in Connections. Note its connectionId.

Every NetLicensing action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/netLicensing/latest/actions/{actionSlug}

You need a MindCloud API Key and a NetLicensing connection. Then call an action such as Get Bundle:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/netLicensing/latest/actions/get-bundle" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected NetLicensing account that should run the action. MindCloud stores and refreshes the NetLicensing credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

NetLicensing actions

All 42 published actions for this NetLicensing version. Each page documents the endpoint, arguments, and response controls.

• POSTCreate Bundle
• POSTCreate License
• POSTCreate Licensee
• POSTCreate Product
• POSTCreate Token
• POSTCreate Transaction
• DELETEDelete Bundle
• DELETEDelete License
• DELETEDelete Licensee
• DELETEDelete Product
• DELETEDelete Token
• GETGet Bundle
• GETGet License
• GETGet License Template
• GETGet Licensee
• GETGet Payment Method
• GETGet Product
• GETGet Product Module
• GETGet Token
• GETGet Transaction
• GETList Bundles
• GETList Countries
• GETList Currencies
• GETList License Templates
• GETList License Types
• GETList Licensees
• GETList Licenses
• GETList Licensing Models
• GETList Payment Methods
• GETList Product Modules
• GETList Products
• GETList Tokens
• GETList Transactions
• POSTObtain Bundle
• PUTTransfer Licenses
• PUTUpdate Bundle
• PUTUpdate License
• PUTUpdate Licensee
• PUTUpdate Payment Method
• PUTUpdate Product
• PUTUpdate Transaction
• GETValidate Licensee

Related apps

More apps on the Universal API, behind the same REST shape. Or browse all apps.

Google SheetsGmailSlackGoogle CalendarGoogle DriveNotionHubSpotGoogle Forms