Skip to main content
Your system must maintain a local cache of customers that have purchased a single-event product that the CMS/OVP solution references when granting the customers access to the single event purchased.
  • Use Case Number: 2-3-03
  • Completed By: Software Developer
  • Estimated Completion Time: <5 days

Design Approach

This use case uses the same design approach as discussed in Manage Subscriber Access to Subscription Content Based on Their Purchased Subscription in that you must develop an endpoint to consume and store entitlement push notifications. On the entitlement start date, for the given entitlement grant Subscribe will issue an entitlement start push notification. You will use a push listener to capture the start entitlement and update the local entitlement cache. Likewise on the entitlement end date Subscribe will issue an entitlement end notification. You will use that notification to record the end date of the given service. Parent topic:Single Event Products

Capture Single-Event Entitlement Start and End Dates Using Push Notifications

To capture single-event entitlement start and end dates:
  1. Implement a push listener endpoint in your system that is capable of receiving https posts from the Subscribe servers. Your authorization system consumes the payload which contains the push entitlement notification message. (See Manage Subscriber Access to Subscription Content Based on Their Purchased Subscription).
  2. On the entitlement start date for the given season, Subscribe issues an entitlement start push notification. You must use your push listener to capture the start entitlement and update you local entitlement cache.
  3. Similarly, on the entitlement end date, Subscribe issues an entitlement end notification. You must use your push listener to capture that notification and update your local entittlement cache to record the end date of the given service.
Parent topic:Manage Customer Access for Single-Event Purchases Using Push Notifications