Entitlement notifications
Bango DVM™ sends Entitlement notifications to keep resellers informed about changes to a consumer’s Product access and related account information. Use these events to synchronize your records and guide consumers through activation, changes, suspension, and termination. An Entitlement represents an individual consumer’s right to access a content provider Product, often provided as part of a Consumer Offer. Notifications describe what happened to that Entitlement; not every notification means its access status has changed.Notification reasons
How to interpret notifications
Account linking and unlinking
ACCOUNT_LINKED confirms the link between an Entitlement and the consumer’s content provider account. ACCOUNT_UNLINKED confirms that the relationship was removed; it does not by itself mean the Entitlement or Product access was terminated. An unlink payload can include extraInformation.source.channelType and extraInformation.source.country to identify where the action originated. For account-management tasks, see Account Management.
Suspension and resumption
SUSPENSION_SUCCESS indicates that the Entitlement was suspended. RESUMPTION_SUCCESS indicates that suspension ended. A resumed Entitlement can return to Pending if it had not been activated before suspension, rather than always becoming Active. Use the returned status as the source of truth. These notifications describe Entitlement API behavior and do not imply that Consumer Offer-level suspend/resume orchestration is supported.
Termination
TERMINATION_PENDING means termination has been scheduled, but access has not yet ended. TERMINATION_SUCCESS confirms the completed outcome. Do not remove access solely on receipt of a pending event.
Product and metadata changes
PRODUCT_UPDATE identifies a change to the associated Product, including a Product Tier change. Use its productKey to synchronize your catalog mapping. METADATA_UPDATE identifies changes to Entitlement metadata, such as custom or extension fields, and does not by itself indicate a Product or access-state change.
Notification payload
Entitlement notifications use a common set of fields, although the exact fields depend on the notification reason. Preserve the exactnotificationReason, identifiers, productKey, and status returned by Bango DVM™. Additional properties such as consumerOffer, extensionData, extraInformation, and event timestamps can be present.
The following payload illustrates ACTIVATION_SUCCESS:
The JSON examples below preserve event-specific fields and casing from the source examples. Some placeholder date values are illustrative rather than populated timestamps. Check the actual response when integrating.
Payload examples
Activation Success
Activation Success
Sent when the consumer’s entitlement has been successfully activated. The entitlement
status is Active. Use this notification to confirm to the consumer that their product is ready to use.Termination Pending
Termination Pending
Sent when the consumer’s entitlement is scheduled for termination at a future date. The entitlement
status is Active-Ending — the consumer still has access until the termination date. A TERMINATION_SUCCESS notification will follow when termination completes.Termination Success
Termination Success
Sent when the consumer’s entitlement has been successfully terminated. The entitlement
status is Cancelled or Revoked. The consumer no longer has access to the product.Product Update
Product Update
Sent when the product associated with the entitlement has changed — for example following an upgrade or downgrade. The
productKey is updated to reflect the consumer’s new product tier. Use this notification to update your records and surface the change to the consumer.Account Linked
Account Linked
Account Unlinked
Account Unlinked
Suspension Success
Suspension Success
Resumption Success
Resumption Success
Metadata Update
Metadata Update
Sent when metadata on the entitlement has been successfully updated. This notification signals that non-product, non-status attributes on the entitlement have changed — for example custom data, source information, or extension fields. Use this notification to keep your records in sync with the latest entitlement metadata.
Recommended reseller actions
| Notification | Suggested Reseller action |
|---|---|
ACTIVATION_SUCCESS | Confirm to the consumer that their product is active and ready to use |
TERMINATION_PENDING | Notify the consumer their access will end on the scheduled date |
TERMINATION_SUCCESS | Confirm to the consumer that their product access has been removed |
PRODUCT_UPDATE | Update your records to reflect the new product tier and notify the consumer of the change |
ACCOUNT_LINKED | Record that the consumer’s entitlement is linked to their Content Provider account, stop any outstanding activation reminders, and confirm to the consumer that their service is ready to use |
ACCOUNT_UNLINKED | Record that the entitlement is no longer linked to a Content Provider account, and prompt the consumer to sign in to or create an account in the Content Provider’s app to restore access |
SUSPENSION_SUCCESS | Update the entitlement status in your system to suspended, and let the consumer know their access to the service is paused and how to restore it |
RESUMPTION_SUCCESS | Update the entitlement status in your system to match the returned status. If Active, confirm to the consumer that their access is restored; if Pending, prompt the consumer to complete activation |
METADATA_UPDATE | Update your records to reflect the latest entitlement metadata |
Key fields explained
string
required
Identifies the notification type. Identifies the Entitlement event. See the notification reasons table above.
string
Present on Entitlement notifications. The unique identifier of the entitlement that changed state.
string
Present on Entitlement notifications. The product key associated with the entitlement. Updated to the new value on
PRODUCT_UPDATE notifications.string
Present on Entitlement notifications. The current status of the entitlement. Examples include
Active, Pending, Suspended, Active-Ending, Cancelled, and Revoked. Match the returned value rather than assuming every event changes the status.
