Resolving PCRF API "ACTIVE package not found" Error When Adding a New Data Top-Up

When attempting to provision or add a new Data Top-Up through the PCRF API, an error message is returned:

{
  "responseCode": 400,
  "responseMessage": "ACTIVE package not found with id: 5710180"
}


This issue typically occurs when an incorrect Top-Up Package ID is used in the API request, or when policies have not been reloaded after creating a new Top-Up. To resolve this, it is important to ensure that the correct package ID is included in the request or that the request is sent using only the Top-Up Package Name.

Solution

1. Verify the Correct Top-Up Package ID

Ensure that the correct Top-Up Package ID is used in API requests. If the Top-Up Package ID is known, it should be explicitly included in the request. If it is unknown, the request can be sent using only the Top-Up Package Name.

2. Corrected API Requests

a.) Using a Valid Top-Up Package ID

If the Top-Up Package ID is known, the request should be formatted as follows:

curl -X POST "http://172.24.182.3:28080/netvertexsm/rest/restful/subscription/subscribeTopUp" \
-H "accept: application/json" -H "Content-Type: application/json" \
-d "{ \"subscriberId\": \"test1234@ftth\", \"topUpPackageId\": \"101ad121-04f3-4fe9-babc-c48efc914934\", \"topUpPackageName\": \"5710180\", \"topUpPackageVersion\": \"1\", \"updateAction\": \"1\"}"


Expected Response:

{
  "responseCode": 200,
  "responseMessage": "SUCCESS",
  "topUpSubscriptions": [
    {
      "topUpSubscriptionId": "34daba2b-b7c9-4233-aa5a-399d59b6a1cc",
      "subscriberIdentity": "test1234@ftth",
      "topUpId": "101ad121-04f3-4fe9-babc-c48efc914934",
      "topUpName": "5710180",
      "topUpVersion": "1",
      "startTime": 1741866477150,
      "endTime": 1757418477150,
      "topUpStatus": "STARTED",
      "priority": 100
    }
  ]
}


b.) Using Only the Top-Up Package Name

If the Top-Up Package ID is unknown, the API request should be formatted without it:

curl -X POST "http://172.24.182.3:28080/netvertexsm/rest/restful/subscription/subscribeTopUp" \
-H "accept: application/json" -H "Content-Type: application/json" \
-d "{ \"subscriberId\": \"test1234@ftth\", \"topUpPackageName\": \"5710180\", \"topUpPackageVersion\": \"1\", \"updateAction\": \"1\"}"


Expected Response:

{
  "responseCode": 200,
  "responseMessage": "SUCCESS",
  "topUpSubscriptions": [
    {
      "topUpSubscriptionId": "34daba2b-b7c9-4233-aa5a-399d59b6a1cc",
      "subscriberIdentity": "test1234@ftth",
      "topUpId": "101ad121-04f3-4fe9-babc-c48efc914934",
      "topUpName": "5710180",
      "topUpVersion": "1",
      "startTime": 1741866477150,
      "endTime": 1757418477150,
      "topUpStatus": "STARTED",
      "priority": 100
    }
  ]
}


3. Reload Policies If Necessary

In some cases, the PCRF system may require a policy reload after creating a new Top-Up package. If the correct Top-Up Package ID is being used but the error persists, perform a policy reload before attempting the request again.

Action Plan

• Ensure the correct topUpPackageId is used in API requests.
• If the ID is unknown, send the request using only the package name.
• Reload policies if necessary after creating a new Top-Up.

By following these steps, the "ACTIVE package not found" error can be successfully resolved when provisioning new Data Top-Ups via the PCRF API.