Query plan purchase request

This GET operation queries a plan purchase request by passing the transactionId in the URL. If successful, you receive an HTTP response code of 200 as well as a JSON response body containing the plan purchase request information.

See HTTP response codes for other response codes.

GET /pcc/spcm/transaction/<transactionId>

HEADER INFO

tenant: <tenantName>

authorisation: HTTP Basic Auth

accept: application/vnd.com.tango.pcc.v2+json

permissions: SPCM_PLAN_TRANSACTION_READ_PERMISSION

URL parameters

There is one mandatory parameter.

Parameter Type Description

transactionId

string

The unique identifier for the transaction.

JSON response

The following example response shows the expected response from passing a recognised transactionId in the URL.

{
    "transactionId": "4190706251458650481450266",
    "planState": "purchased",
    "planTxnState": "complete",
    "planID": "123456"
}


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

transaction 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