Unblock subscriber’s core plan

This PUT operation unblocks a subscriber’s core plan by deactivating any rule violations that might be blocking it. If successful, you receive an HTTP response code of 200 and a small JSON success response.

PUT /pcc/spcm/subscribers/<msisdn>/unblockCore

HEADER INFO

tenant: <tenantName>

authorisation: HTTP Basic Auth

accept: application/JSON

permissions: SPCM_PLAN_UPDATE_PERMISSION

URL parameters

There is one mandatory parameter.

Parameter Type Description

msisdn

string (max 255)

The subscriber’s MSISDN in international format.

Response

If you receive a 200 HTTP response code (valid subscriber), you will receive a JSON payload similar to the following:

For other HTTP response codes, see HTTP response codes. 
{
    "status": "success"
}


HTTP response codes

Code Description

200

success!

207

Multistatus response

Check out HTTP statuses for more details.
This is not applicable to all operations.

400

malformed request

401

unauthorised; bad username or password

403

forbidden; user does not have appropriate privileges

404

{api-object} not found

409

conflict with target resource

This often occurs if the item already exists, such as a plan, group, or name.
This is not applicable to all operations.

412

failed validation; this typically means that a property was not set or a value is out of range.

example
HTTP 412
{
  "errors" : [
        {
          "field" : "name",
          "description" : "name is mandatory"
        }
    ]
}

422

failed processing (after passing validation).

example
HTTP 422
{
    "message": "Subscriber max plan count exceeded",
    "errorCode": 1
}

500

internal error

example
HTTP/1.1 500
{
    "message": "Internal server error - [Failed to get session information]",
    "status": "error"
}

503

request rejected due to overload