Please review the FAQs below to see if we can answer your question here.
Please check that you are:
- Adding an
Authorizationheader in your requests
- Base64-encoding your credentials in the
- Using the correct credentials for either the sandbox or production environment
If you are still having issues, please contact our support team who will be able to help.
Some requests are not supported by all partners. If this is the case, you will always get this response code on this route for a specific request.
If you are getting this error on every type of request on a route, please contact our support team who will be able to help.
The echo endpoint is optional, but useful. It enables you to:
- Validate your credentials and the base URL
- Confirm that the Bango Resale API is currently available
It depends on the merchant and the products/services offered. Bango will configure each route to restrict the number of entitlements per customer as required.
If the activation URL expires, you can request a new one using the /activationInfo endpoint. See the API Reference for more details.
The customerIdentifier is the reseller’s unique identifier for the customer.
The sharedCustomerId is a unique identifier for this customer on a specific route and is shared with that merchant as well as the reseller.
The entitlementId is the globally unique identifier for a single entitlement.
The sharedCustomerId and entitlementId are generated by the Bango Platform.
When you send a request to cancel an entitlement, you are asking the merchant to terminate the subscription at the end of the current billing cycle. The customer continues to have access to that entitlement until the end of the subscription period they have already paid for.
When you send a request to revoke an entitlement, you are asking the merchant to terminate the subscription immediately.
Yes. The notificationUrl is set at the entitlement level. If you want to use the same notificationUrl for all entitlements, you can.
If your customer is not eligible for the product/offer through you because they have already had the offer or are already accessing the entitlement directly, the merchant will not activate the entitlement. Instead, the merchant will send a revoke notification with:
- reasonCategory: ACTIVATION_ROLLBACK
- reasonCode: CUSTOMER_NOT_ELIGIBLE