Get action for a usage rule definition

This GET operation retrieves the action for a specific usage rule definition by passing the usageRuleDefinitionId in the URL. If successful, you receive an HTTP response code of 200 and a JSON response containing the action.

See HTTP response codes for other response codes.

GET /pcc/spcm/planDefinitions/<planDefinitionId>/usageRuleDefinitions/<usageRuleDefinitionId>/action

HEADER INFO

tenant: <tenantName>

authorisation: HTTP Basic Auth

accept: application/JSON

permissions: SPCM_PLAN_DEFINITION_READ_PERMISSION

URL parameters

There are two mandatory parameters.

Parameter Type Description

planDefinitionId

integer

A unique identifier for a plan definition which was assigned by the server upon creating the plan definition.

usageRuleDefinitionId

integer

The id of the usage rule definition.

JSON response

This exmaple shows a JSON response containing the action information for the specified usage rule definition (passed in the URL).

{
    "id": 50,
    "name": "80 percent usage"
}


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

usage rule definition 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