Get Operator and Circle By Mobile Number API

The Get Prepaid Recharge PlansAPI for getting prepaid plans. It will provide all the available prepaid recharge plans available for a given agent ID, circle ID and operator ID.

Environment

Test Environmenthttps://bbps-sb.payu.in .
Production EnvironmentContact your Account Manager to get access to the production environment

๐Ÿ“˜

Note:

This API requires an access token using the Get Token API with the scope as read_operator_circle. For more information, refer to Get Token API - BBPS.

Sample request
curl --location --request GET 'https://payu-nbc/v2/nbc/getOperatorAndCircleInfo?agentId={agentId}&mobileNumber={mobileNumber}' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <token>'
Response parameters
Field NameDescription
codeThe global response code and can be any of the following:

- 0: If web service call failed
- 1: if web service call succeeded
statusThe status of the API command and can be any of the following:

- SUCCESS
- FAILURE
payloadIt will contain a list of biller categories. For more information, refer to the payload table.

payload

Theย payloadย parameter contains the values in a JSON format are described in the following table:

FieldDescription
Success Scenario
circlesInfoThis field contains the following set of values for each circle in an JSON array format:

- operatorAndCircleInfo : contains information regarding operator & circle details like operator code, operator name , and circle reference ID of the customerโ€™s mobile number entered as
an input.
Failure Scenario
refIdFor failure scenarios, this parameter contains the reference ID.
typeThis field contains the value as operator_circle_fetch for this API.
errorFor failure scenarios, this field contains the error message in an array format.
messageThis field contains the message type as operator_fetch_request_failed for this API.
additionalParamsFor failure scenarios, this field contains the additional fields related to billers in an array format. If there is no any additional info, it will be null.โ€ฏ
Sample response

Success scenario

{
   "code":200,
   "status":"SUCCESS",
   "payload":{
      "operatorName":"OPERATOR_1",
      "operatorId":"OPERATOR_ID_1",
      "plansInfo":[
         {
            "planName":"<plan_name_1>",
            "price":"<plan_price_1>",
            "validity":"<validity_1>",
            "talkTime":"<talk_time_1>",
            "packageDescription":"<description_1>",
            "planType":"<plan_type>"
         },
         {
            "planName":"<plan_name_1>",
            "price":"<plan_price_1>",
            "validity":"<validity_1>",
            "talkTime":"<talk_time_1>",
            "packageDescription":"<description_1>",
            "planType":"<plan_type>"
         }
      ]
   }
}

Failure scenario

"code":600,
"status":"FAILURE",
"payload":{
   "errors":[
      {
         "reason":"<error Message>",
         "errorCode":"<Error Code>"
      }
   ],
   "refId":null,
   "type":"mobile_plans",
   "message":"mobile_plans_fetch_failed",
   "additionalParams":{
      "Key: "value1", 
    "Key2": "value2", 
    "Key3": "value3"\" 
    } 
} 
}"

Request parameters

Language
Authorization
Bearer
Click Try It! to start a request and see the response here!