Since NetLicensing API (RESTful) is based on open standards, you can use any web development language to access the API; there are also lots of pre-built libraries for interacting with NetLicensing.
NetLicensing exposes all available service's functionality via an Application Programming Interface (API).
To access the API methods you will need a NetLicensing vendor account. If you do not have one already, signup here.
|Endpoint||Allowed operations||Supported authentication method (?)|
|Product Module Services||LISTGETCREATEUPDATEDELETE|
|License Template Services||LISTGETCREATEUPDATEDELETE|
|Payment Method Services||LISTGETUPDATE|
Structure of the RESTful URIs
NetLicensing API (RESTful) provide access to resources (data entities) via URI paths. To use a RESTful API, your application will make an HTTP(S) request and parse the response. The NetLicensing API (RESTful) uses JSON or XML as its response format
and the standard HTTP methods like GET, PUT, POST and DELETE (see endpoints documentation to find out which methods are supported by particular resource).
URIs for NetLicensing API (RESTful) resources have the following structure:
<host> - NetLicensing API host name -
go.netlicensing.io. Backup host name -
<port> - NetLicensing API port, can be omitted, NetLicensing uses standard https port 443.
<resource> - represents named resource (e.g. product, license etc.), you'll find the resource name on the wiki page describing corresponding resource
<query> - parameters passed with the request (see below)
Resources may require additional input parameters, in which case parameters must be passed as query string for GET and DELETE methods and as a message body (payload) for POST and PUT.
Parameters are passed in '
key=value' form, separated by '
&' symbol. When passed in a message body (for POST and PUT), it corresponds to the Form Encoded Data format. Use the following request header in this case:
Depending on the value passed in the
Accept: field of the request header, NetLicensing will reply in XML or JSON format. The structure of the response is documented in XML Schema Definition that can be downloaded at https://go.netlicensing.io/schema/context/netlicensing-context-2.1.xsd.
All values are transmitted over HTTP in text form. The following table summarizes the text representation of non-trivial data types:
Timestamps follow XML Schema Part 2: Datatypes Second Edition / D ISO 8601 Date and Time Formats. On input it may be specified as date only (corresponds to xsd:date) or date + time (corresponds to xsd:dateTime). On a java backend, javax.xml.bind.DatatypeConverter is used for conversion.
Always represented by two fields: decimal "price" and "currency" - 3-character code according to ISO 4217. Currently only "EUR" is supported.
- List of HTTP status codes - http://en.wikipedia.org/wiki/List_of_HTTP_status_codes