Create a new entitlement
Authorizations
Basic authentication
Headers
Request unique identifier. If present, this id will be used for idempotency.
Body
The entitlement JSON you want to create
User unique identifier.
"4407123456789"
Merchant unique identifier. For example, "BANGO".
"BANGO"
Entitlement product unique identifier. For example, "30_DAYS_MUSIC".
"BangoMusic"
The endpoint where all POST notifications will be sent after subscription creation. The body of the POST request will contain the entitlement information in https://developer.bango.com/resale/api-ref/notifications.
"https://www.example.com/notification/a25100b8-4e0c-4e37-b921-cac9cb1e930f"
Entitlement display name. For example, "30 days Bango music" (optional).
"30 days of Bango music"
Entitlement offer. For example, "BUNDLE" (optional).
null
Entitlement expiry date in UTC ISO 8601 format. Null if no expiry (yyyy-MM-ddThh:mm:ssZ)
null
Entitlement auto-suspension date in UTC ISO 8601 format. Null if no auto-suspension (yyyy-MM-ddThh:mm:ssZ)
null
External identifier for the Entitlement from the Reseller.
"124130d2-2cbc-45a1-ab9b-dfa8b67a2e63"
Response
Entitlement created and activated successfully.
Unique identifier representing a specific entitlement.
"a25100b8-4e0c-4e37-b921-cac9cb1e930f"
User unique identifier.
"4407123456789"
Entitlement product unique identifier. For example, "BangoMusic".
"BangoMusic"
Entitlement offer. For example, "BUNDLE".
null
Merchant unique identifier. For example, "BANGO".
"BANGO"
Date and time when the entitlement was created, in UTC ISO 8601 format (yyyy-MM-ddThh:mm:ssZ)
Date and time when the entitlement was activated, in UTC ISO 8601 format (yyyy-MM-ddThh:mm:ssZ)
Date and time when the entitlement ended due to cancellation or revoke, in UTC ISO 8601 format (yyyy-MM-ddThh:mm:ssZ)
"0001-01-01T00:00:00Z"
Entitlement expiry date in UTC ISO 8601 format. Null if no expiry (yyyy-MM-ddThh:mm:ssZ)
"0001-01-01T00:00:00Z"
"OK"
"Success"
Entitlement status. Possible values are:
- "ACTIVE": The entitlement has been successfully activated
- "CANCELLED": The entitlement has been cancelled.
- "REVOKED": The entitlement has been revoked. This usually happens on fraud and user contract termination cases.
- "SUSPENDED": The entitlement has been suspended.
- "PENDING": The entitlement has been initiated, but the user has not yet finalized the activation process.
- "FAILED": The entitlement failed
- "ACTIVE-ENDING": The entitlement is ending at the end of the current period.
ACTIVE, CANCELLED, REVOKED, SUSPENDED, PENDING, FAILED, ACTIVE-ENDING "ACTIVE"
Bango generated id shared between reseller and merchant for this customer (contact support for setup)
"414b3019-0c28-4d14-9c5f-6217b8bd1e3e"
Entitlement display name. For example, "30 days Bango music".
"30 days Bango music"
Code or token use for the entitlement activation.
null
Entitlement auto-suspension date in UTC ISO 8601 format. Null if no auto-suspension (yyyy-MM-ddThh:mm:ssZ)
null
Date and time when the entitlement failed, in UTC ISO 8601 format (yyyy-MM-ddThh:mm:ssZ)
"0001-01-01T00:00:00Z"
Date and time when the entitlement was suspended, in UTC ISO 8601. format (yyyy-MM-ddThh:mm:ssZ)
null
Date and time when the entitlement was resumed, in UTC ISO 8601. format (yyyy-MM-ddThh:mm:ssZ)
null
External identifier for the Entitlement from the Reseller.
"124130d2-2cbc-45a1-ab9b-dfa8b67a2e63"
Accepts a dynamic list of key-value pairs to cover custom data needs

