All notable changes to this product and documentation will be listed in this file.
Added section Configuring the Automatic Charge Interval.
Validation error responses returned with HTTP 400 (Bad Request) from the PUT /line-items endpoint now use the key message instead of errors.
API v1.0 behavior
In v1.0, validation errors were returned under the errors key:
{
"errors": [
"$.attributes.overdraftLimit: string found, integer expected",
"$.attributes: property 'resetFrequency' is not defined in the schema and the schema does not allow additional properties"
]
}API v1.1 behavior
Starting with v1.1, the same validation errors are returned under the message key:
{
"message": [
"$.attributes.overdraftLimit: string found, integer expected",
"$.attributes.resetFrequency: integer found, string expected"
]
}Initially, this change applies only to the PUT /line-items endpoint. All other endpoints and response formats remain unchanged.
The status codes returned in responses for elastic access requests—covering both session-based and non-session-based scenarios—have been updated. In version 1.0 they were represented as three-digit codes. In version 1.1, these status codes are now expressed as four-digit codes. This change has been implemented to avoid confusion with standard HTTP response codes.
For an example, see Access request for elastic tokens.
The response to a session heartbeat request has been updated to improve clarity and consistency when a session is in a non-operable state.
Behavior in Version 1.0
- A 403 response was returned if the session was terminated. However, this did not distinguish between terminated, failed, or disconnected states.
- A 409 response was returned if the session was locked.
Behavior in Version 1.1
- The request will fail with a 409 response whenever the session is in any non-operable state (e.g., terminated, failed, disconnected, or locked).
- The response includes an error message indicating the current state of the session, providing clearer diagnostic information.
The Dynamic Monetization User Guide and API Reference have been merged into a single, comprehensive document, offering simplified navigation and a more cohesive experience for developers and users alike.
The older versions of the Dynamic Monetization User Guide and API Reference will be retired in November 2025.
The Rules of Access APIs enable license administrators to define and enforce access control policies for token consumption from elastic line items in a Dynamic Monetization environment. The rules specify which user or device can consume tokens, based on specific conditions. This helps administrators maintain accurate and proportionate consumption of the allocated budget.
- Added Rules of Access section in the User Guide
- Added tutorial Controlling Access with Conditions and Actions
- Added section Rules of Access in API Reference
Introduction of Dynamic Monetization, a new cloud service that allows technology companies to introduce flexible monetization models for connected software and devices. The first monetization model supported in this release is Elastic Access.