GETGet District Discome (UPPCL)

Resolve the district-level distribution company code required by UPPCL (operator 190).

GET/customer/payment/bbps/operators/190/district-discome

Some electricity billers require a district-level distribution company (discome) code. This applies to operator 190 (UPPCL) only — no other biller needs it, and the path is fixed to 190 rather than parameterised.

Show the agent each label and send the matching value as district_discome on both Fetch Bill and Pay Bill.

The list is returned under param_attributes.list_elements, not under data.

Request

Query parameters

Field	Type	Required	Description
`initiator_id`	string	required	Registered mobile number of the API user (see Platform Credentials).e.g. 9962981729
`client_ref_id`	string	optional	Unique reference ID per API call, generated by your system (max 20 characters).e.g. 2026010100123456789

initiator_idstringRequired

Registered mobile number of the API user (see Platform Credentials).

example: 9962981729

client_ref_idstringoptional

Unique reference ID per API call, generated by your system (max 20 characters).

example: 2026010100123456789

These headers authenticate and sign every request. See How Auth Works for details.

Field	Type	Required	Description
`developer_key`	string	required	Static API key issued to your account after KYC.
`secret-key`	string	required	Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).
`secret-key-timestamp`	string	required	Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.
`content-type`	string	required	application/jsone.g. application/json

developer_keystringRequired

Static API key issued to your account after KYC.

secret-keystringRequired

Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).

secret-key-timestampstringRequired

Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.

content-typestringRequired

application/json

example: application/json

Response types

response_type_id	Meaning	Next step
`2110`	District list returned — pass the chosen `value` as `district_discome` when fetching the bill.	Fetch BBPS Bill
`2434`	Districts could not be fetched. The envelope still carries `status: 0`, so branch on this id rather than on `status`.	—

Responses

2110District list returned — pass the chosen `value` as `district_discome` when fetching the bill.Next:Fetch BBPS Bill

statusnumber
Primary success indicator (0 = success).
messagestring
Human-readable response / error message.
response_status_idnumber
Granular status id; see the shared error-codes table.
response_type_idnumber
A unique id for every possible response shape (success or error) — useful for client logic branching and analytics.
dataobject
API-specific response payload.
- param_attributesobject
  Wrapper for the district list — returned at the top level of the response, not under `data`.
  - list_elementsarray
    One entry per UPPCL district.
    - labelstring
      District name to show the agent.
    - valuestring
      The `district_discome` value to pass to Fetch Bill and Pay Bill for operator 190.

Next steps

import { EpsClient } from "@ekoindia/eps-sdk";

const client = new EpsClient({

developerKey: process.env.EPS_DEVELOPER_KEY,

accessKey: process.env.EPS_ACCESS_KEY,

initiatorId: "9962981729",

environment: "sandbox",

});

const result = await client.call("bbps-district-discome");

console.log(result);

{

"response_status_id": 0,

"param_attributes": {

"list_elements": [

{

"label": "Agra",

"value": "Agra-DVVNL"

{

"label": "Lucknow",

"value": "Lucknow-MVVNL"

{

"label": "Kanpur Nagar",

"value": "Kanpur Nagar-KESCO"

{

"label": "Varanasi",

"value": "Varanasi-PUVNL"

}

]

"response_type_id": 2110,

"message": "Success",

"status": 0

}

Request

Query parameters

Response types

Responses

Next steps

Related