Patch Entitlement
Request sent to the merchant to update entitlement information like Product detail. Expected responses as defined below.
Authorizations
Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
Headers
Request unique identifier. This id should be used for idempotency.
Body
The entitlement JSON you want to update
Unique identifier used on activation
"6e37a4b5-8cb9-465b-88a9-ad5eb02596be"
Unique user identifier, as identified by Bango
"1549053185"
Entitlement product unique identifier. For example, "30_DAYS_MUSIC".
"30_DAYS_MUSIC"
Unique reseller identifier
"XYZ_RESELLER"
Bango generated id shared between reseller and merchant for this customer (contact support for setup)
"414b3019-0c28-4d14-9c5f-6217b8bd1e3e"
ENUM parameter to instruct the type of benefits action needed as part of the update request only if a change is required. This enum is used to suspend and resume entitlements using the update method.
SUSPENDED, NORMAL Unique identifier representing a specific customer of the reseller not anonymised. This value will only be sent by Bango if the Merchant and Reseller both approve the sharing of this data
The offer given to the user for the merchant service. For example, "FREE_FOR_6_MONTHS".
"FREE_FOR_6_MONTHS"
Entitlement status. Possible values are:
- "ACTIVE": The entitlement has been successfully activated
- "SUSPENDED": The entitlement has been suspended.
- "PENDING": The entitlement has been initiated, but the user has not yet finalized the activation process.
- "ACTIVE-ENDING": The entitlement is ending at the end of the current period.
ACTIVE, SUSPENDED, PENDING, ACTIVE-ENDING "ACTIVE"

