Electricity Bill Verification
1 endpoint · Core API
What is Electricity Bill Verification? API simplifies the process of confirming customers' identities by cross-referencing their electricity bills. This ensures the legitimacy of the customer and mitigates the risk of fraudulent activities. Leveraging online utility bill verification systems is a secure and efficient method for institutions and entities to authenticate their customers' credibility. All that's needed for this process are specific customer credentials. This streamlined approach enhances security measures and provides peace of mind for businesses and organizations.
Benefits
- 1. Enhances security by verifying customers' identities through their electricity bills
- 2. Mitigates the risk of fraudulent activities and unauthorized access
- 3. Streamlines the verification process for institutions and entities
- 4. Provides peace of mind by ensuring the legitimacy of customers
What you can do
API verifies electricity bills and customer IDs issued by multiple Electricity Distribution Companies throughout India, ensuring secure authentication and validation of information.
You must send the electricity board yourself.
This API requires a service_provider code in the request (for example BSES_DL, TATA_DL, MAHAVITRAN) alongside the consumer_id. The biller is not auto-detected from the consumer ID — pick the code for the board that issued the bill from the table below.
We currently support 58 provider codes covering 59 electricity boards across India (BSES_DL serves both BSES Yamuna and BSES Rajdhani).
Supported electricity boards
Use Ctrl+F / Cmd+F to search by code or board name.
Delhi
service_provider | Electricity board |
|---|---|
BSES_DL | BSES Yamuna / BSES Rajdhani |
TATA_DL | Tata Power Delhi |
Maharashtra
service_provider | Electricity board |
|---|---|
MAHAVITRAN | MSEDCL (Mahavitaran) |
TATA_MUMBAI | Tata Power Mumbai |
BEST_MH | BEST Mumbai |
TORRENT_BHIWANDI | Torrent Power Bhiwandi |
Gujarat
service_provider | Electricity board |
|---|---|
UGVCL | Uttar Gujarat Vij Company |
PGVCL | Paschim Gujarat Vij Company |
MGVCL | Madhya Gujarat Vij Company |
DGVCL | Dakshin Gujarat Vij Company |
TORRENT_AHD | Torrent Power Ahmedabad |
TORRENT_SURAT | Torrent Power Surat |
TORRENT_DAHEJ | Torrent Power Dahej |
Karnataka
service_provider | Electricity board |
|---|---|
BESCOM | Bangalore Electricity Supply Company |
MESCOM | Mangalore Electricity Supply Company |
CESCOM | Chamundeshwari Electricity Supply Company |
GESCOM | Gulbarga Electricity Supply Company |
HESCOM | Hubli Electricity Supply Company |
Tamil Nadu (TANGEDCO)
service_provider | Region |
|---|---|
CHENNAI_NORTH | Chennai North |
CHENNAI_SOUTH | Chennai South |
COIMBATORE | Coimbatore |
MADURAI | Madurai |
TRICHY | Trichy |
ERODE | Erode |
VELLORE | Vellore |
VILLUPURAM | Villupuram |
TIRUNVELVEL | Tirunelveli |
Uttar Pradesh
service_provider | Electricity board |
|---|---|
UPPCL | Uttar Pradesh Power Corporation |
KESCO | Kanpur Electricity Supply Company |
TORRENT_AGRA | Torrent Power Agra |
Rajasthan
service_provider | Electricity board |
|---|---|
JAIPUR | Jaipur Vidyut Vitran Nigam |
AJMER | Ajmer Vidyut Vitran Nigam |
JODHPUR | Jodhpur Vidyut Vitran Nigam |
Madhya Pradesh
service_provider | Electricity board |
|---|---|
MPWZ | MP Paschim Kshetra (West) |
MPCZ | MP Madhya Kshetra (Central) |
MPEZ | MP Poorv Kshetra (East) |
Andhra Pradesh / Telangana
service_provider | Electricity board |
|---|---|
APSPDCL | AP Southern Power Distribution Company |
APEPDCL | AP Eastern Power Distribution Company |
TSSPCL | Telangana Southern Power Distribution Company |
Haryana
service_provider | Electricity board |
|---|---|
DHBVN | Dakshin Haryana Bijli Vitran Nigam |
UHBVN | Uttar Haryana Bijli Vitran Nigam |
Bihar
service_provider | Electricity board |
|---|---|
NBPDCL | North Bihar Power Distribution Company |
SBPDCL | South Bihar Power Distribution Company |
West Bengal
service_provider | Electricity board |
|---|---|
WBENGAL | WBSEDCL |
CESC | CESC Kolkata |
Other states and union territories
service_provider | Electricity board | State / UT |
|---|---|---|
APDCL | Assam Power Distribution Company | Assam |
CSPDCL | Chhattisgarh State Power Distribution Company | Chhattisgarh |
JBVNL | Jharkhand Bijli Vitran Nigam | Jharkhand |
KERALA | KSEB | Kerala |
PSPCL | Punjab State Power Corporation | Punjab |
HPSEB | Himachal Pradesh State Electricity Board | Himachal Pradesh |
ORISSA | Odisha distribution utilities | Odisha |
MeECL | Meghalaya Energy Corporation | Meghalaya |
TRIPURA | Tripura State Electricity Corporation | Tripura |
GOA_ELEC | Goa Electricity Department | Goa |
UPAY_GOA | Goa (UPAY) | Goa |
CH_ELEC | Chandigarh Electricity Department | Chandigarh |
DAMAN_DIU | Daman & Diu Electricity Department | Daman & Diu |
Request notes
consumer_idis required: 9 to 13 letters or digits, as printed on the bill.service_provideris required and must be one of the codes above.regMobileNois required whenservice_providerisKERALA(10-digit mobile number registered with the connection, starting with 6, 7, 8 or 9). For other boards it is optional.
Get electricity bill verification details
Headers
- X-API-KEYstringrequiredYour secret API key for the environment you are calling (Stage and Live use different keys).
- X-API-APP-IDstringrequiredThe App ID issued together with the key.
- Content-Typestringrequiredapplication/json
Body parameters
application/json- consentstringrequiredRequired. The end user's consent to this verification. Send `Y`.minLength 1default Y
- consent_textstringrequiredRequired. The consent statement shown to the end user. Send the default text from the sample.minLength 1default I hear by declare my consent agreeme…
- request_idstringoptionalOptional. Your own id to correlate this call in your logs. A unique id is generated if you leave it out.nullable
- consumer_idstringrequiredRequired. Consumer ID printed on the electricity bill. 9 to 13 letters or digits (A-Z, a-z, 0-9), no spaces or symbols.minLength 9maxLength 13pattern ^[a-zA-Z0-9]+$default 1012345678
- service_providerstringrequiredRequired. Code of the electricity board that issued the bill, for example BESCOM. Must be one of the supported codes. Allowed values: APSPDCL, APEPDCL, APDCL, NBPDCL, SBPDCL, CESC, CH_ELEC, CSPDCL, DAMAN_DIU, TATA_DL, BSES_DL, GOA_ELEC, UPAY_GOA, UGVCL, PGVCL, MGVCL, DGVCL, TORRENT_AHD, TORRENT_SURAT, TORRENT_AGRA, TORRENT_BHIWANDI, TORRENT_DAHEJ, DHBVN, UHBVN, HPSEB, JBVNL, MESCOM, BESCOM, CESCOM, GESCOM, HESCOM, KERALA, MPWZ, MPCZ, MPEZ, TATA_MUMBAI, MAHAVITRAN, BEST_MH, MeECL, ORISSA, PSPCL, JAIPUR, AJMER, JODHPUR, CHENNAI_NORTH, VILLUPURAM, COIMBATORE, ERODE, MADURAI, TRICHY, TIRUNVELVEL, VELLORE, CHENNAI_SOUTH, TSSPCL, TRIPURA, KESCO, UPPCL, WBENGAL.minLength 1default BESCOM
- regMobileNostringconditionalConditional: required when service_provider is KERALA, optional for other boards. Mobile number registered with the electricity account: 10 digits starting with 6, 7, 8 or 9.nullablelength 10pattern ^[6-9]\d{9}$
Sample request body
Responses
200OK
- successbooleanoptionalNo description.
- statusCodeinteger (int32)optionalNo description.default 200
- messagestringoptionalNo description.nullabledefault XXXXX
- dataobjectoptionalResponse model containing electricity bill verification details.
12 fields
- bill_nostringoptionalBill number of the electricity bill.nullable
- bill_due_datestringoptionalDue date for the bill payment.nullable
- consumer_numberstringoptionalConsumer number associated with the electricity connection.nullable
- bill_amountstringoptionalBill amount for the current billing cycle.nullable
- bill_issue_datestringoptionalDate when the bill was issued.nullable
- mobile_numberstringoptionalMobile number registered with the electricity account.nullable
- amount_payablestringoptionalTotal amount payable for the bill.nullable
- total_amountstringoptionalTotal cumulative amount including arrears.nullable
- addressstringoptionalAddress of the electricity connection.nullable
- consumer_namestringoptionalName of the consumer as registered with the provider.nullable
- email_addressstringoptionalEmail address associated with the consumer account.nullable
- bill_datestringoptionalDate of the electricity bill.nullable
- messagesarray<string>optionalNo description.nullable
- request_idstringoptionalNo description.nullable
- isBillablebooleanoptionalWhether this request was charged: true if it was, false if not. Errors always show false. Flows that finish later (ITR Fetch, SHCIL eStamp, DigiLocker, eSign) show false here, because the charge is made when the result is ready. eSign charges each signer when they complete signing. DigiLocker deducts the credit when the link is created and refunds it automatically if the link expires before the user completes it.
400Bad Request
- dataobjectoptionalNo description.
- messagesarray<string>optionalNo description.nullable
- request_idstringoptionalNo description.nullable
- successbooleanoptionalNo description.default false
- messagestringoptionalNo description.nullabledefault XXXXX
- isBillablebooleanoptionalNo description.
- statusCodeinteger (int32)optionalNo description.default 400
401Unauthorized
- dataobjectoptionalNo description.
- messagesarray<string>optionalNo description.nullable
- request_idstringoptionalNo description.nullable
- successbooleanoptionalNo description.default false
- messagestringoptionalNo description.nullabledefault XXXXX
- isBillablebooleanoptionalNo description.
- statusCodeinteger (int32)optionalNo description.default 401
500Internal Server Error
- dataobjectoptionalNo description.
- messagesarray<string>optionalNo description.nullable
- request_idstringoptionalNo description.nullable
- successbooleanoptionalNo description.default false
- messagestringoptionalNo description.nullabledefault XXXXX
- isBillablebooleanoptionalNo description.
- statusCodeinteger (int32)optionalNo description.default 500