# Changelog

All notable changes to this product and documentation will be listed in this file.

## July 30, 2026: Introducing Resettable Line Items

Dynamic Monetization now supports *resettable line items*. Resettable line items automatically replenish a configured quantity at regular intervals throughout the line item's lifecycle, enabling recurring allocations without requiring entitlement renewals or manual intervention.

The new topic [Resettable Line Items](/products/dynamicmonetization/guides/resettable-line-items) describes how to configure and use resettable line items.

## July 30, 2026: Consumption Limits Documentation

Documentation for *consumption limits* is now available: [Consumption Limits](/products/dynamicmonetization/guides/consumption-limits).

## March 30, 2026: Introducing Consumption Limits

Elastic Access now provides *consumption limits* which allow end customers to regulate how quickly requesters may consume tokens associated with a line item. They serve as an important budgetary control mechanism within Elastic Access, helping organizations prevent unexpected or excessive usage during a line item’s lifecycle. By applying consumption limits, customers can align usage patterns with internal budgets, operational constraints, and the intended consumption cadence of their purchased entitlements.

**Quick Links:**

- [Consumption Limits](/products/dynamicmonetization/apis/openapi-spec/consumption-limits) in API Reference
- [Consumption Limits](/products/dynamicmonetization/guides/consumption-limits) in User Guide


## February 19, 2026: User Guide Update About Charge Interval

Added section [Configuring the Automatic Charge Interval](/products/dynamicmonetization/guides/sessions/managing-sessions#configuring-the-automatic-charge-interval).

## February 12, 2026: Error Response Format Updated

Validation error responses returned with HTTP **400 (Bad Request)** from the [`PUT /line-items`](/products/dynamicmonetization/apis/openapi-spec/line-items/addactivation) endpoint now use the key `message` instead of `errors`.

**API v1.0 behavior**

In v1.0, validation errors were returned under the `errors` key:

```json
{
  "errors": [
    "$.attributes.overdraftLimit: string found, integer expected",
    "$.attributes: property 'resetFrequency' is not defined in the schema and the schema does not allow additional properties"
  ]
}
```

br
**API v1.1 behavior**

Starting with v1.1, the same validation errors are returned under the `message` key:

```json
{
    "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.

## December 16, 2025: Version 1.1 Replacing Version 1.0

### Updated Elastic Access Reponse

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](/products/dynamicmonetization/apis/openapi-spec/non-session-access-request/postaccessrequest#non-session-access-request/postaccessrequest/t=response&c=200&path=requesteditems/status).

### Updated Session Heartbeat Response Behaviour

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.


## September 23, 2025: Unified Documentation for Dynamic Monetization

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.

## August 2025: Rules of Access

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.

### Documentation Updates for Rules of Access

- Added [Rules of Access](/products/dynamicmonetization/guides/rules-of-access) section in the User Guide
- Added tutorial [Controlling Access with Conditions and Actions](/products/dynamicmonetization/tutorials/controlling-access)
- Added section [Rules of Access](/products/dynamicmonetization/apis/openapi-spec/rules-of-access) in API Reference


## June 4, 2024: Initial Release

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.