Configuration Values in Dynamic Monetization
Use the /configuration API to manage configuration values that control how your customers can access and consume line items.
Note:This section provides only a short overview. For detailed information about the /configuration API, see the API documentation, section https://fnoapi-dynamicmonetization.redoc.ly/#tag/Configuration.
Getting the Configuration
Send a GET request to /configuration to receive the current configuration. If any values have been modified, the response also includes details about the modification date and the token key ID that was used to change the value.
Modifying the Configuration
Send a PATCH request to /configuration to change any values. In the request body, specify the name and value parameters for the configuration value that you want to add or modify.
Configurable Values
You can configure the following values.
|
Configuration Value |
Description |
Default Setting |
|
timezone.tolerant |
Allows tokens to be consumed up to 12 hours before a line item’s start date and up to 12 hours after its end date. This ensures that client applications can operate for a full day at the start of a line item no matter where they are located in the world; and that they can operate for a full day at the expiration of a line item no matter where they are in the world. Note:Elastic Access has no knowledge of where the client software application is located. It is just “tolerant” by allowing all applications an extra half day at the start and expiration. Important:Setting timezone.tolerant to true has a negative consequence for producers, who will be extending the life of a line item by a complete day in total. The benefit to producers, however, is that their customers have a good experience, with no interruption to their productivity even when they are located in the extreme timezones at +12 and -12 hours from UTC. Supported values: true (enabled) and false (disabled). |
false |