Mahavitaran electricity bill, meter and outage data

Maharashtra State Electricity Distribution Co.Ltd. · Utilities

Mahavitaran is the official consumer Android app from Maharashtra State Electricity Distribution Co. Ltd. (MSEDCL), serving electricity customers across Maharashtra outside the Mumbai licensee areas. Households, shops and agricultural-pump users can view and pay energy bills, review past bills and receipts, submit camera meter readings, raise service complaints and follow new-connection applications. Its services also include prepaid-meter recharge, Go Green paperless billing, feeder-outage information, postpaid-to-prepaid conversion, load changes and changes of name. Web Self Service (WSS) sign-in brings together the consumer numbers linked to an account, while guest bill lookup and payment are available without a full WSS login. BillDesk, Paytm and Paynimo are among the app's payment options.

MSEDCL billing cycles pair billMonthYYMM with billAmount, dueDate, promptPayAmount, afterDueDateAmount and paidYN. Settlement records add TransactionID, Amount and BillMonth, with PaidOnline, PGTransID and BankReferenceID tying each receipt to its gateway and bank reference, while linked connections carry ConNumber, MeterNumber and hasSmartMeterYN. Smart-meter records supply CURRENT_BALANCE, MTD_CONSUMPTION and READING; prepaid-recharge options specify minPayableAmount and amountMultipleOf.

Finance teams can use billing cycles and receipts for ERP reconciliation, and facilities teams can combine meter balances with recharge constraints to flag low prepaid balances. Feeder records join feederName and feederKV to dclLoss, collectionEfficiency and billingEfficiency for each distribution transformer, alongside outage startTime, endTime and reason for operations planning. New-connection teams can follow applicationStatus and payableEstimateAmount alongside service-request progress in serviceRequestStatus. openData Studio turns these electricity-account records into callable open data for reconciliation, energy monitoring and connection-tracking integrations.

Screenshots

API surface

The endpoints and request/response examples below are reconstructed from the app's interface — illustrative, not a live capture.

WSS account sign-in

POST /v1/wss-sessions osint

Signs the WSS holder in and returns AccountDetails plus the ConsumerList of consumer numbers used on every later bill, meter and complaint call.

Auth: None on this call. Body carries loginId and pass; the same pair is later sent as HTTP Basic on authenticated calls.

loginId
pass
deviceOS
appVersion
ResponseStatus
AccountExist
EnableMeterReading
AccountDetails
accId
Name
EmailId
MobileNo
ConsumerList
ConName
ConNumber
BU
BUName
MeterNumber
hasSmartMeterYN
amisp
billingType
DTCCode
circleName

POST /v1/wss-sessions HTTP/1.1
Content-Type: application/json

{
  "loginId": "demo.wss.user",
  "pass": "<example-password>",
  "deviceOS": "ANDROID",
  "appVersion": 83
}

{
  "ResponseStatus": "SUCCESS",
  "AccountExist": "YES",
  "EnableMeterReading": "YES",
  "AccountDetails": {
    "accId": "DEMO-ACCOUNT-001",
    "loginId": "demo.wss.user",
    "Name": "DEMO CONSUMER",
    "EmailId": "[email protected]",
    "MobileNo": "<demo-mobile>",
    "ConsumerList": [
      {
        "ConName": "DEMO CONSUMER",
        "ConNumber": "DEMO-CONSUMER-001",
        "BU": "DEMO-BU",
        "BUName": "DEMO BILLING UNIT",
        "MeterNumber": "DEMO-METER-001",
        "hasSmartMeterYN": "YES",
        "amisp": "demo-provider",
        "billingType": "postpaid",
        "DTCCode": "DEMO-DTC-001",
        "circleName": "DEMO CIRCLE"
      }
    ]
  }
}

Fetch latest energy bill

GET /v1/energy-bills/latest opendata

Returns the current electricity bill for a consumer number: billAmount, billMonthYYMM, dueDate, prompt-pay rebate and paidYN used on the view-bill screen.

Auth: HTTP Basic from the WSS loginId and password (Authorization: Basic), plus Client-Os=ANDROID, Client-Os-Version and Client-Version headers. Guest lookup by consumer number (cno) is also accepted on this call.

responseStatus
consumerExistYN
applicableAmount
applicableAmountId
bill
consumerNumber
consumerName
billingUnit
billingUnitName
circleName
billNumber
billMonthYYMM
billDate
billAmount
dueDate
promptPayAmount
promptPayDate
afterDueDateAmount
consumption
paidYN
enablePaymentYN
meterStatus
cutoffDate

GET /v1/energy-bills/latest?consumerNumber=DEMO-CONSUMER-001 HTTP/1.1
Authorization: Basic <example-basic-credentials>

{
  "responseStatus": "SUCCESS",
  "consumerExistYN": "YES",
  "applicableAmount": "1840.50",
  "applicableAmountId": "1",
  "bill": {
    "consumerNumber": "DEMO-CONSUMER-001",
    "consumerName": "DEMO CONSUMER",
    "billingUnit": "DEMO-BU",
    "billingUnitName": "DEMO BILLING UNIT",
    "circleName": "DEMO CIRCLE",
    "billNumber": "DEMO-BILL-001",
    "billMonthYYMM": "202610",
    "billDate": "05-Oct-26",
    "billAmount": "1840.50",
    "dueDate": "20-Oct-26",
    "promptPayAmount": "1795.00",
    "promptPayDate": "12-Oct-26",
    "afterDueDateAmount": "1910.00",
    "consumption": "196",
    "paidYN": "NO",
    "enablePaymentYN": "YES",
    "meterStatus": "NORMAL",
    "cutoffDate": "20261025"
  }
}

Fetch billing history

GET /v1/energy-bills/history opendata

Lists prior billing cycles for a consumer number with CurrentBill, Consumption, BillMonth and LastReceiptAmount shown on the bill-history table.

Auth: HTTP Basic from the WSS loginId and password (Authorization: Basic), plus Client-Os=ANDROID, Client-Os-Version and Client-Version headers.

CurrentBill
billDate
BillMonth
Status
Consumption
IsRecentYn
LastReceiptAmount
LastReceiptDate

GET /v1/energy-bills/history?ConNumber=DEMO-CONSUMER-001 HTTP/1.1
Authorization: Basic <example-basic-credentials>

[
  {
    "CurrentBill": "1840.50",
    "billDate": "05-Oct-26",
    "BillMonth": "Oct-26",
    "Status": "LIVE",
    "Consumption": "196",
    "IsRecentYn": "YES",
    "LastReceiptAmount": "1720.00",
    "LastReceiptDate": "18-Sep-26"
  },
  {
    "CurrentBill": "1720.00",
    "billDate": "05-Sep-26",
    "BillMonth": "Sep-26",
    "Status": "LIVE",
    "Consumption": "181",
    "IsRecentYn": "NO",
    "LastReceiptAmount": "1655.00",
    "LastReceiptDate": "16-Aug-26"
  }
]

Fetch payment receipts

GET /v1/settlement-records openfinance

Returns payment receipts for a consumer number with Amount, TransactionID, BillMonth and PaidOnline used on the receipts list.

Auth: HTTP Basic from the WSS loginId and password (Authorization: Basic), plus Client-Os=ANDROID, Client-Os-Version and Client-Version headers.

ResponseStatus
consumerExistYN
isUpdated
Receipts
ReceiptID
TransactionID
ConsumerNo
ConsumerName
BillMonth
BillingUnit
BillDueDate
PC
Amount
TransactionDateTime
PaidOnline
Paidviaapp
PGTransID
ReceiptType
StatusMessage
BankCode
BankReferenceID

GET /v1/settlement-records?ConsumerNo=DEMO-CONSUMER-001 HTTP/1.1
Authorization: Basic <example-basic-credentials>

{
  "ResponseStatus": "SUCCESS",
  "consumerExistYN": "YES",
  "isUpdated": "YES",
  "Receipts": [
    {
      "ReceiptID": "DEMO-RECEIPT-001",
      "TransactionID": "DEMO-TRANSACTION-001",
      "ConsumerNo": "DEMO-CONSUMER-001",
      "ConsumerName": "DEMO CONSUMER",
      "BillMonth": "Sep-26",
      "BillingUnit": "DEMO-BU",
      "BillDueDate": "20-Sep-26",
      "PC": "01",
      "Amount": "1720.00",
      "TransactionDateTime": "18-09-2026 09:30:12",
      "PaidOnline": "YES",
      "Paidviaapp": "YES",
      "PGTransID": "DEMO-GATEWAY-001",
      "ReceiptType": "ENERGY",
      "StatusMessage": "SUCCESS",
      "BankCode": "DEMO-BANK",
      "BankReferenceID": "DEMO-BANK-REFERENCE-001"
    }
  ]
}

Fetch consumer connection info

GET /v1/service-connections/profile osint

Returns service-request consumer info: name, billing-unit name, address lines, pin, Mobile and isAgConsumerYn for the selected consumer number.

Auth: HTTP Basic from the WSS loginId and password (Authorization: Basic), plus Client-Os=ANDROID, Client-Os-Version and Client-Version headers.

ResponseStatus
ConsumerExist
ConsumerInfo
ConsumerName
ConsumerNumber
BUName
AddressLine1
AddressLine2
AddressLine3
pin
Email
Mobile
phone
isAgConsumerYn

GET /v1/service-connections/profile?ConsumerNumber=DEMO-CONSUMER-001&BU=DEMO-BU HTTP/1.1
Authorization: Basic <example-basic-credentials>

{
  "ResponseStatus": "SUCCESS",
  "ConsumerExist": "YES",
  "ConsumerInfo": {
    "ConsumerName": "DEMO CONSUMER",
    "ConsumerNumber": "DEMO-CONSUMER-001",
    "BUName": "DEMO BILLING UNIT",
    "AddressLine1": "DEMO ADDRESS LINE 1",
    "AddressLine2": "DEMO ADDRESS LINE 2",
    "AddressLine3": "DEMO CIRCLE",
    "pin": "<demo-postcode>",
    "Email": "[email protected]",
    "Mobile": "<demo-mobile>",
    "phone": "<demo-phone>",
    "isAgConsumerYn": "NO"
  }
}

Smart-meter current reading
GET /v1/meter-readings/latest opendata
Returns the AMISP smart-meter header for a consumer number: READING, CURRENT_BALANCE, MTD_CONSUMPTION and METER_NUMBER shown on the smart-meter dashboard.
Auth: HTTP Basic from the WSS loginId and password (Authorization: Basic), plus Client-Os=ANDROID, Client-Os-Version and Client-Version headers.
- METER_NUMBER
- READING
- READING_DATE_TIME
- MD
- CURRENT_BALANCE
- MTD_CONSUMPTION
- PREV_MTH_CONSUMPTION
- PREV_MTH_READING
- UPDT_DATETIME
```
GET /v1/meter-readings/latest?amisp=demo-provider&ConNumber=DEMO-CONSUMER-001 HTTP/1.1
Authorization: Basic <example-basic-credentials>
```
```
{
  "METER_NUMBER": "DEMO-METER-001",
  "READING": "93205",
  "READING_DATE_TIME": "2026-10-26 06:15:00",
  "MD": "3.2",
  "CURRENT_BALANCE": "1240.00",
  "MTD_CONSUMPTION": "118",
  "PREV_MTH_CONSUMPTION": "181",
  "PREV_MTH_READING": "93087",
  "UPDT_DATETIME": "2026-10-26 06:16:12"
}
```

Prepaid recharge info

GET /v1/prepayment/options openfinance

Confirms a prepaid consumer and returns minPayableAmount, amountMultipleOf and suggestedAmounts used on the prepaid recharge screen.

Auth: HTTP Basic from the WSS loginId and password (Authorization: Basic), plus Client-Os=ANDROID, Client-Os-Version and Client-Version headers.

ResponseStatus
isPrepaidConsumerYn
enablePaymentYn
minPayableAmount
amountMultipleOf
suggestedAmounts
mobile
email
consumer
ConName
ConNumber
billingType
MeterNumber

GET /v1/prepayment/options?ConNumber=DEMO-CONSUMER-001 HTTP/1.1
Authorization: Basic <example-basic-credentials>

{
  "ResponseStatus": "SUCCESS",
  "isPrepaidConsumerYn": "YES",
  "enablePaymentYn": "YES",
  "minPayableAmount": 100,
  "amountMultipleOf": 50,
  "suggestedAmounts": [
    "200",
    "500",
    "1000"
  ],
  "mobile": "<demo-mobile>",
  "email": "[email protected]",
  "consumer": {
    "ConName": "DEMO CONSUMER",
    "ConNumber": "DEMO-CONSUMER-001",
    "billingType": "prepaid",
    "MeterNumber": "DEMO-METER-001"
  }
}

Feeder statistics and outages

GET /v1/distribution-feeders/overview opendata

Returns feederName, feederKV, DCL loss and the outages list (startTime, endTime, reason) for a distribution-transformer code.

Auth: HTTP Basic from the WSS loginId and password (Authorization: Basic), plus Client-Os=ANDROID, Client-Os-Version and Client-Version headers.

responseStatus
feederName
feederKV
dclMonth
collectionEfficiency
billingEfficiency
dclGroup
dclLoss
outages
startTime
endTime
reason

GET /v1/distribution-feeders/overview?DTCCode=DEMO-DTC-001 HTTP/1.1
Authorization: Basic <example-basic-credentials>

{
  "responseStatus": "SUCCESS",
  "feederName": "DEMO-FEEDER-11KV",
  "feederKV": "11",
  "dclMonth": "Oct-26",
  "collectionEfficiency": "94.2",
  "billingEfficiency": "96.1",
  "dclGroup": "A",
  "dclLoss": "8.4",
  "outages": [
    {
      "startTime": "2026-10-12 14:20:00",
      "endTime": "2026-10-12 16:05:00",
      "reason": "PLANNED MAINTENANCE"
    }
  ]
}

List service-request complaints

GET /v1/support-cases opendata

Lists open and closed service requests for a consumer number with serviceRequestID, serviceRequestStatus and serviceRequestTypeName shown on the complaints list.

Auth: HTTP Basic from the WSS loginId and password (Authorization: Basic), plus Client-Os=ANDROID, Client-Os-Version and Client-Version headers.

responseStatus
serviceRequests
serviceRequestID
consumerNumber
consumerBU
consumerName
serviceRequestTypeName
serviceRequestMajorTypeName
serviceRequestSubTypeName
serviceRequestStatus
createdDateTime
canBeClosed
requestDetail
closureRemark

GET /v1/support-cases?consumerNumber=DEMO-CONSUMER-001&consumerBU=DEMO-BU HTTP/1.1
Authorization: Basic <example-basic-credentials>

{
  "responseStatus": "SUCCESS",
  "serviceRequests": [
    {
      "serviceRequestID": "DEMO-CASE-001",
      "consumerNumber": "DEMO-CONSUMER-001",
      "consumerBU": "DEMO-BU",
      "consumerName": "DEMO CONSUMER",
      "serviceRequestTypeName": "NO POWER",
      "serviceRequestMajorTypeName": "SUPPLY",
      "serviceRequestSubTypeName": "FUSE OFF",
      "serviceRequestStatus": "Assigned",
      "createdDateTime": "2026-10-12 14:22:00",
      "canBeClosed": "NO",
      "requestDetail": "Illustrative supply interruption",
      "closureRemark": ""
    }
  ]
}

New-connection application status

GET /v1/connection-applications/progress opendata

Looks up a new-connection application by select/value and returns applicationStatus, payableEstimateAmount and requestedLoad for the NC tracker.

Auth: HTTP Basic from the WSS loginId and password (Authorization: Basic), plus Client-Os=ANDROID, Client-Os-Version and Client-Version headers.

responseStatus
validInputDetails
paid
enablePaymentYn
payableEstimateAmount
payableEstimateNumber
msg
ErrorMessage
applicationDetail
applicationID
consumerNo
consumerName
applicationDate
billUnit
category
serviceType
supplyType
requestedLoad
applicationStatus
circleName
mobileNumber

GET /v1/connection-applications/progress?applicationID=DEMO-APPLICATION-001 HTTP/1.1
Authorization: Basic <example-basic-credentials>

{
  "responseStatus": "SUCCESS",
  "validInputDetails": "YES",
  "paid": "NO",
  "enablePaymentYn": "YES",
  "payableEstimateAmount": "8450.00",
  "payableEstimateNumber": "DEMO-ESTIMATE-001",
  "msg": "Estimate generated",
  "ErrorMessage": "",
  "applicationDetail": {
    "applicationID": "DEMO-APPLICATION-001",
    "consumerNo": "DEMO-CONSUMER-001",
    "consumerName": "DEMO CONSUMER",
    "applicationDate": "12-Oct-26",
    "billUnit": "DEMO-BU",
    "category": "LT",
    "serviceType": "NEW CONNECTION",
    "supplyType": "1PH",
    "requestedLoad": "3",
    "applicationStatus": "ESTIMATE ISSUED",
    "circleName": "DEMO CIRCLE",
    "mobileNumber": "<demo-mobile>"
  }
}

Go Green paperless-bill status

GET /v1/bill-delivery/preferences opendata

Returns Go Green enrolment state for a consumer number: registrationExistsYN, emailId and restrictRegistrationYN used on the paperless-bill screen.

Auth: HTTP Basic from the WSS loginId and password (Authorization: Basic), plus Client-Os=ANDROID, Client-Os-Version and Client-Version headers.

responseStatus
consumerExistsYN
billExistsYN
registrationExistsYN
isLiveYN
consumerNumber
consumerName
billingUnit
billingUnitName
billMonthYYMM
emailId
pc
restrictRegistrationYN
restrictRegistrationReason
notes

GET /v1/bill-delivery/preferences?consumerNumber=DEMO-CONSUMER-001 HTTP/1.1
Authorization: Basic <example-basic-credentials>

{
  "responseStatus": "SUCCESS",
  "consumerExistsYN": "YES",
  "billExistsYN": "YES",
  "registrationExistsYN": "NO",
  "isLiveYN": "YES",
  "consumerNumber": "DEMO-CONSUMER-001",
  "consumerName": "DEMO CONSUMER",
  "billingUnit": "DEMO-BU",
  "billingUnitName": "DEMO BILLING UNIT",
  "billMonthYYMM": "202610",
  "emailId": "[email protected]",
  "pc": "01",
  "restrictRegistrationYN": "NO",
  "restrictRegistrationReason": "",
  "notes": ""
}

Meter-reading pre-data

GET /v1/meter-submissions/context opendata

Loads meter-reading submission pre-data: MeterNumber, PrevReading, MREnabled and solarRtYN before the consumer posts a camera reading.

Auth: HTTP Basic from the WSS loginId and password (Authorization: Basic), plus Client-Os=ANDROID, Client-Os-Version and Client-Version headers.

ResponseStatus
consumerExistsYN
billingUnit
billMonthYYMM
MeterNumber
PrevReading
MREnabled
MREnabledUpto
mobileNumber
solarRtYN
expPrevReading
genMeterNumber
genMeterDigits
genPrevReading
impExpMeterDigits

GET /v1/meter-submissions/context?ConNumber=DEMO-CONSUMER-001 HTTP/1.1
Authorization: Basic <example-basic-credentials>

{
  "ResponseStatus": "SUCCESS",
  "consumerExistsYN": "YES",
  "billingUnit": "DEMO-BU",
  "billMonthYYMM": "202610",
  "MeterNumber": "DEMO-METER-001",
  "PrevReading": "93087",
  "MREnabled": "YES",
  "MREnabledUpto": "2026-10-31",
  "mobileNumber": "<demo-mobile>",
  "solarRtYN": "NO",
  "expPrevReading": "0",
  "genMeterNumber": "",
  "genMeterDigits": "",
  "genPrevReading": "",
  "impExpMeterDigits": "5"
}

Fetch registered contact details

GET /v1/account-contacts osint

Returns the registered EmailId, MobileNo and Uid for a consumer number on the contact-details screen.

Auth: HTTP Basic from the WSS loginId and password (Authorization: Basic), plus Client-Os=ANDROID, Client-Os-Version and Client-Version headers.

ResponseStatus
ConsumerExist
isInfoAvailable
EmailId
MobileNo
Uid
Consumer
ConName
ConNumber
BU
BUName

GET /v1/account-contacts?ConNumber=DEMO-CONSUMER-001 HTTP/1.1
Authorization: Basic <example-basic-credentials>

{
  "ResponseStatus": "SUCCESS",
  "ConsumerExist": "YES",
  "isInfoAvailable": "YES",
  "EmailId": "[email protected]",
  "MobileNo": "<demo-mobile>",
  "Uid": "",
  "Consumer": {
    "ConName": "DEMO CONSUMER",
    "ConNumber": "DEMO-CONSUMER-001",
    "BU": "DEMO-BU",
    "BUName": "DEMO BILLING UNIT"
  }
}

Data categories

energy bills
payment receipts
smart-meter readings
feeder outages
service requests
consumer accounts
new-connection applications

Where teams use this data

ERP energy-bill reconciliation
Nightly jobs pull billAmount, billMonthYYMM and paidYN for each ConNumber on a WSS account and match them to the AP ledger before the dueDate.
Smart-meter and prepaid energy audit
Facilities teams join CURRENT_BALANCE and MTD_CONSUMPTION with prepaid minPayableAmount so sites with AMISP meters can flag balance run-out before supply cuts.
Feeder-outage operations window
Dispatch boards overlay feederName outages (startTime, endTime, reason) on the DTC so agritech pumps and shop floors wait out planned maintenance instead of raising duplicate no-power tickets.
New-connection pipeline tracking
Builders poll applicationStatus and payableEstimateAmount on each NC applicationID until paid flips, then hand the consumerNo to billing onboarding.

Frequently asked questions

What identifiers link Mahavitaran electricity records?

A WSS account contains a ConsumerList of ConNumber values. Bills, receipts and service requests use the consumer number, with the billing unit BU where needed. Smart-meter records also use the AMISP provider identifier, and feeder records link to DTCCode. The published API paths and example values are illustrative, not live service addresses or working account details.

Does guest bill lookup require a WSS login?

The latest bill can be viewed using a consumer number without a full WSS login, and the app also lets guests pay a bill from the consumer number alone. Signed-in account functions use HTTP Basic authentication with the WSS loginId and password; the examples show placeholders rather than working credentials.

Which electricity distributor and region does this cover?

Mahavitaran covers MSEDCL electricity customers in Maharashtra outside the Mumbai licensee areas. It does not represent BEST, Adani Electricity Mumbai or Tata Power Mumbai.

Which feeder and smart-meter fields are available?

Feeder records carry feederName, feederKV, dclMonth, dclLoss, collectionEfficiency and billingEfficiency, plus an outages list with startTime, endTime and reason, keyed by the DTCCode of the consumer's distribution transformer. Smart-meter records carry METER_NUMBER, READING, READING_DATE_TIME, CURRENT_BALANCE, MTD_CONSUMPTION and PREV_MTH_CONSUMPTION for AMISP-linked connections.

Apps similar to Mahavitaran

Adani Electricity — Adani Electricity is the official consumer app of Adani Electricity, Mumbai — one of the city licensees outside MSEDCL's Maharashtra concession — for paying the monthly bill, downloading bill copies, registering no-supply complaints, checking outage status and submitting a meter reading.
My Tata Power- Consumer App — My Tata Power is Tata Power's official consumer app for viewing and paying electricity bills, monitoring usage, live-chat support and rooftop-solar tools, from the Mumbai-based utility that distributes power in parts of Mumbai alongside BEST and Adani Electricity.
Torrent Power Connect — Torrent Power Connect lets customers pay online, submit a meter reading, call a technician for supply issues and track complaints, covering Torrent Power's licensed cities plus Bhiwandi in Maharashtra, which MSEDCL operates as a Torrent distribution franchisee.
TNEB Mobile App(Official) — TNEB Mobile App(Official) is Tamil Nadu Power Distribution Corporation's (TNPDCL) electricity app for Quick Pay, card/UPI/net-banking bill payment, usage views, and downloading bills or e-receipts.
BESCOM Mithra — BESCOM Mithra is Bangalore Electricity Supply Company's consumer app for online bill payment, consumption and payment history, scheduled and unscheduled outage information, and GPS-tracked complaint restoration.
KSEB — KSEB is Kerala State Electricity Board's official self-service app, with Web Self Service registration, Quick Pay without an account, and up to 24 months of bill, consumption and payment history across as many as 30 consumer numbers.
myBijulee — myBijulee is Assam Power Distribution Company Limited's official app for viewing and paying postpaid bills, prepaid-meter recharge, complaint logging, new-connection applications and load or category changes.
CESCAPPS - Pay Bill — CESCAPPS is CESC Limited's Kolkata-area consumer app for viewing, downloading and paying electricity bills, applying for a new connection or load extension, reporting supply outages and opting into e-bills.

More Utilities apps

Topics

Mahavitaran data API
MSEDCL electricity bills
Maharashtra consumer number
electricity payment receipts
AMISP smart meter reading
prepaid meter balance
feeder outage data
Go Green paperless billing
new connection status
energy bill reconciliation
distribution transformer feeder loss
prepaid recharge minimum amount

Need this app's data API integrated?

We deliver scoped integrations for any named app — from USD 500 with source-code handoff, or hosted access billed per call. Tell us the data you need.

NDA + SOW on every engagement
Delivery in 3–7 days
Payment only after acceptance
Work scoped to authorized use

Get a quote

Mahavitaran electricity bill, meter and outage data

Screenshots

API surface

WSS account sign-in

Fetch latest energy bill

Fetch billing history

Fetch payment receipts

Fetch consumer connection info

Smart-meter current reading

Prepaid recharge info

Feeder statistics and outages

List service-request complaints

New-connection application status

Go Green paperless-bill status

Meter-reading pre-data

Fetch registered contact details

Data categories

Where teams use this data

ERP energy-bill reconciliation

Smart-meter and prepaid energy audit

Feeder-outage operations window

New-connection pipeline tracking

Frequently asked questions

Apps similar to Mahavitaran

More Utilities apps

All Languages Translator

Enel São Paulo

File Commander - File Manager

Genius Scan - PDF Scanner

Topics

Need this app's data API integrated?

Mahavitaran electricity bill, meter and outage data

Screenshots

API surface

WSS account sign-in

Fetch latest energy bill

Fetch billing history

Fetch payment receipts

Fetch consumer connection info

Smart-meter current reading

Prepaid recharge info

Feeder statistics and outages

List service-request complaints

New-connection application status

Go Green paperless-bill status

Meter-reading pre-data

Fetch registered contact details

Data categories

Where teams use this data

ERP energy-bill reconciliation

Smart-meter and prepaid energy audit

Feeder-outage operations window

New-connection pipeline tracking

Frequently asked questions

Related apps

Apps similar to Mahavitaran

More Utilities apps

All Languages Translator

Enel São Paulo

File Commander - File Manager

Genius Scan - PDF Scanner

Topics

Need this app's data API integrated?