How does license validation work in NetLicensing?

Q: How does license validation work in NetLicensing?

Your application sends POST /core/v2/rest/licensee/{licenseeNumber}/validate, signed in with an API key, along with any parameters the licensing model needs, such as a nodeSecret or a floating sessionId. NetLicensing then takes all of that licensee’s active licenses and runs them through the rules of each product module’s licensing model. The response has one ProductModuleValidation entry per module, with valid and whatever else the model returns (expires, remainingQuantity, per-feature results), plus a ttl timestamp. Your application turns features on or off from that result and reuses it until the ttl. For most applications, that’s the only API call they ever need. More detail is in Software Licensing API: Architecture and Examples and the validate reference.

Question

What happens when my application validates a license?

Answer

Your application sends POST /core/v2/rest/licensee/{licenseeNumber}/validate, signed in with an API key, along with any parameters the licensing model needs, such as a nodeSecret or a floating sessionId.

NetLicensing then takes all of that licensee’s active licenses and runs them through the rules of each product module’s licensing model. The response has one ProductModuleValidation entry per module, with valid and whatever else the model returns (expires, remainingQuantity, per-feature results), plus a ttl timestamp.

Your application turns features on or off from that result and reuses it until the ttl. For most applications, that’s the only API call they ever need. More detail is in Software Licensing API: Architecture and Examples and the validate reference.

Last updated October 25, 2026 · Edit this page on GitHub