Subscription event types

Understand the event types supported by Digital River.

In Commerce API, understanding and using event types is crucial for building efficient and responsive integrations. Event types follow a straightforward convention: resource.event, which streamlines the development process. These events are essential for tracking various changes and actions, allowing developers to tailor their applications to react in real-time to activities within the commerce environment.

Subscribing to event types lets your application receive notifications about specific occurrences, such as delayed payment reminders, subscription updates, or renewal reminders. This guide will explore the available event types within the Commerce API, providing examples and insights on effectively integrating them into your solutions. Whether setting up a new webhook or managing existing ones, this section will ensure you know how to maximize the events available in the Commerce API.

You can create a webhook, view the details of an existing webhook, and find the latest list of event types supported in Global Commerce.

Understanding the different types of subscription events in the Commerce API can help you effectively manage and respond to changes in your subscription lifecycle. Below is a brief description of each event type:

• Subscription action processed event: This event occurs when any action on a subscription has been processed, indicating a change or update has been completed.

• Subscription cancelled event: Triggered when a subscription is canceled either by the subscriber or due to a failed payment, marking the end of the subscription lifecycle.

• Subscription created event: Occurs when a new subscription is created, signaling the start of a new subscriber relationship.

• Subscription credit card expired event: Triggered when the credit card associated with a subscription has expired, potentially impacting future payments.

• Subscription payment failed event: Occurs when a subscription payment attempt fails, requiring attention to resolve payment issues and maintain the subscription.

• Subscription payment information changed event: Triggered when the payment information for a subscription is updated, ensuring future transactions use the current payment method.

• Subscription renewal reminder event: This event occurs before a subscription is due to renew, serving as a prompt to remind the subscriber of the upcoming renewal.

• Subscription renewed event: Triggered when a subscription is successfully renewed, extending the subscription period.

• Subscription updated event: This event occurs when any details of a subscription (excluding payment information) are changed, keeping the subscription terms current.

• Subscription trial converted event: Triggered when a trial subscription is converted to a paid subscription, marking the transition from a trial to a full subscription.

• Subscription trial renewal reminder event: This event occurs before a trial subscription is due to renew, either as another trial period or converting to a full subscription, reminding the subscriber of the impending renewal.

By integrating these events into your application, you can create a dynamic and responsive subscription management system that adapts in real time to the needs of your subscribers.

Subscription action processed event, subscription cancelled event, subscription created event, subscription credit card expired event, subscription payment failed event, subscription payment information changed event, subscription renewal reminder event, subscription renewed event, subscription updated event, subscription trial converted event, subscription trial renewal reminder event.