License Deactivation Offline

8min
Currently we support trial, perpetual and consumption license types for offline activation purposes
This endpoint handles offline deactivation of a license for a specific computer identified by hardware ID via ls_deactivation.req file
POST
Request
Header Parameters
Date
required
String
eq. Thu, 17 Nov 2022 20:51:35 GMT
Authorization
required
String
See signing of the License API calls article.
Body Parameters
Payload
required
Object
Base64 encoded JSON
Curl
Node.js
JS
Python
Ruby
require "uri"
require "net/http"

url = URI("/api/v4/deactivate_offline")

http = Net::HTTP.new(url.host, url.port);
request = Net::HTTP::Post.new(url)
request["Accept"] = "application/json"
request["Date"] = "string"
request["Authorization"] = "string"
request.body = "{\"Payload\":\"Object\"}"

response = http.request(request)
puts response.read_body

require "uri"
require "net/http"

url = URI("/api/v4/deactivate_offline")

http = Net::HTTP.new(url.host, url.port);
request = Net::HTTP::Post.new(url)
request["Accept"] = "application/json"
request["Date"] = "string"
request["Authorization"] = "string"
request.body = "{\"Payload\":\"Object\"}"

response = http.request(request)
puts response.read_body
Responses
200
400

﻿
Payload
If using multipart/form-data file form parameter is obligatory
{
   "app_ver":"LicenseSpringSample1.2.0.0",
   "hardware_id":"A53F-0CBC-15FC-7E81-BF35-A720-A575-7C0C-8815-0463-DB78-E674-D140-CF15-85BB-EC01",
   "ip_local":"10.10.103.157",
   "os_hostname":"ddd.aaaa.com",
   "os_ver":"Microsoft Windows NT 6.2.9200.0",
   "product":"TP",
   "sdk_ver":"4.3.1",
   "license_key":"FUH3-4E7A-LZJL-7JTP",
   "username": "[email protected]", // if user based licenses
   "api_key":"11abafc3-10b2-474a-b818-aaaf97c7512e",
   "date":"Tue, 14 May 2019 14:26:07 GMT",
   "request":"activation",
   "request_id":"2edf98fe-29cb-4c7c-b1fa-7ed7ea2acb6b",
   "signature":"\/cK16QtcRBIPRMyy2igaIUJVCNa2lz2ZazjaaHD\/BRw="
}
Optional fields in the payload
To sync consumptions from offline license to the LicenseSpring:
{
  "consumptions": 5,  // local license consumption that is not yet synced with the backend
  "product_features": [ // array of local consumptions of features
    {
      "consumptions": 75,
      "feature": "feature_code_1"
    }
  ]
}
List of exceptions
missing_headers (400): some headers are missing
when missing authorization or date headers
missing_parameters (400): some parameters are missing in the request: different, parameters
when no request body at all or no file found in request body
authorization_missing_params (400): some parameters are missing in authorization: different, parameters
when has request body but request body is not properly base 64 encoded
when file is missing in request body
when license_key or hardware_id body parameters are missing
when data body parameter is missing
when api_key parameter is missing
Guide on using offline Licenses
 If any aspect of the offline licensing model remains unclear or raises questions, we encourage you to explore our in-depth guide on ﻿Offline License Activation﻿﻿
This resource offers a comprehensive explanation of the offline licensing process, how it operates, and ways to utilize its advantages for your specific software applications
Updated 25 Sep 2024
Did this page help you?
License Activation Offline
License Check