Revoking a third-party product entitlement – non-SSP deployment
Request
To revoke the status of a third-party product entitlement,, the CRM system should send a POST request to:
https://<host>:<port>/tpes/v1/operator/entitlements/{entitlementId}/actions/revoke
Headers
x-correlation-id
– identifier for logging, to correlate messages across a call flowAuthorization
– Keycloak access token (see Accessing operator APIs using Keycloak)nv-tenant-id
– the tenant ID
Mandatory arguments
entitlementId
(in URL) – the ID of the entitlement to be cancelledcancelReasonCategory
(in body) – the revocation reason category (see table below)cancelReasonCode
– (in body) the revocation reason code (see table below)
Valid revocation categories and reasons are as follows:
Category | Reason code |
---|---|
|
|
| |
| |
| |
| |
| |
| |
|
|
| |
|
|
| |
| |
| |
|
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
Optional arguments
cancelReasonDescription
– a description of the revocation reason
Example
A POST request with the following body will update the status of the entitlement whose ID is specified in the URL:
{
"cancelReasonCategory": "REVOKED",
"cancelReasonCode": "ACCOUNT_TERMINATED"
}
Response
A successful request returns an HTTP 200 status.
If the request is awaiting confirmation from the third-party provider, the request returns an HTTP 202 status. When OPF receives this confirmation, it notifies your CRM system – see Handling third-party product entitlement changes.
A bad request returns an HTTP 400 status.
A forbidden request returns an HTTP 403 status.
If the specified tenant does not exist, the request returns an HTTP 404 status.
See the Third Party Entitlement Service (TPES) API documentation for the specific error codes and their meanings.