Skip to main content
Skip table of contents

Deleting a third-party product entitlement

Overview

If the self-care portal needs to delete a third-party product entitlement, it should call the CRM Gateway (CRM-GW) endpoint described below and not the Rights Manager (RMG) entitlement deletion endpoint.

This ensures that Bango is notified of the change so that it can remove the subscription.

Request

To delete a third-party product entitlement, send a DELETE request to:

BASH
https://<host>:<port>/crm-gateway/v2/rmg/v1/entitlements/{entitlementId}

Headers

  • x-correlation-id  – identifier for logging, to correlate messages across a call flow

  • Authorization – Keycloak access token (see Accessing operator APIs using Keycloak)

  • Content-Type: application/json

Mandatory arguments

  • entitlementId – the ID of the entitlement to be deleted

Optional arguments

None

Response

A successful request returns an HTTP 200 status.

A bad request returns an HTTP 400 status.

A forbidden request (invalid token) returns an HTTP 403 status.

If the specified tenant does not exist, the request returns an HTTP 404 status.

See the CRM Gateway API documentation for the specific error codes and their meanings.

Example

A successful request returns the following response:

JSON
{
  "deletedCount": 1
}

See also

CRM Gateway API documentation

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.