> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slm.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Customer Access for Single-Event Purchases Using Push Notifications

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](2301_r_manageSubscriberAccessContent#) 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.

* **[Capture Single-Event Entitlement Start and End Dates Using Push Notifications](../topics/2303_r_manageSubscriberAccessSingleEvent#)**

**Parent topic:**[Single Event Products](../topics/r_singleEventProducts)

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

* Contact Vindicia support to configure the Subscribe Entitlement Push Notifications to point to the URL of your push listener.
* Create the single-event Product in the Product catalog (see [Configure Single-Event Products](2106_r_configureSingleEventPortal#)).
* Enable customers to purchase the single event Product using the Subscribe APIs (see [Enable Customers to Purchase a Single-Event Product Without Purchasing a Subscription](2206_r_purchaseSingleEventWithoutSubscriptionAPI#)).

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](2301_r_manageSubscriberAccessContent#)).

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](../topics/2303_r_manageSubscriberAccessSingleEvent#)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.