Offline Request Schema

overview as part of our ongoing efforts to strengthen security, we have introduced schema version 2 (v2) for offline requests this update enhances request integrity by ensuring the entire payload is signed and verifiable schema version 2 (v2) – changes schema v2 introduces full payload signing and request versioning key changes schema version field every request now includes a schema version field allows license api to detect and handle the request format hmac sha256 signature the entire request json is signed using hmac sha256 with the client secret or shared key ensures all fields are protected from tampering nested request object the signed request is wrapped in an outer json object the request field must remain a proper json object (not a string) to allow correct parsing and signature verification on the license api side example (v2) benefits of v2 full payload integrity all fields are signed, including previously optional fields backward compatible older sdks using v1 requests will still work while v2 enables enhanced security simplifies license api parsing and signature verification enabling schema version 2 to enable v2 for your offline requests log in to the vendor platform in the left sidebar, go to settings → preferences locate the minimum offline request schema version section select v2 from the dropdown list by default, this setting is version 1 , so you must switch it to version 2 to start generating v2 offline requests offline schema v2 requires an sdk version that supports v2 please check the sdk release notes to ensure compatibility before enabling