Access requests can be made as part of a session. This allows the following:
- Repeating, sequencing, or varying a number of activities over a period.
- Charging tokens repeatedly at regular intervals so that total charges are proportional to the duration of use.
- Ensuring that the software can continue use of items over an extended period without having to repeat requests to Elastic Access at precisely the right time.
- Charging for repeated use up-front rather than retrospectively, therefore avoiding “extending credit” to the customer
Sessions are initiated, managed, and terminated programmatically by the client application that makes an access request. Actions related to sessions are performed using the /api/<version>/sessions endpoint of the Dynamic Monetization REST APIs (see Request a new session).
Charge Interval Assumption
The following documentation assumes an automatic charge interval of one hour. The automatic charge interval can be configured for anything from 10 minutes to 24 hours. Refer to the section on Configuring the Automatic Charge Interval for more information.