Energisa On API integration and OpenData utility workflows

1) Invoice and duplicate bill API

Extract current and historical invoice objects, due dates, barcode/PIX references, and payment status fields. Typical use: build automated overdue reminders and connect utility receivables into finance stacks that already ingest banking statements.

2) Consumption history synchronization

Capture month-level usage series, billed kWh, and trend markers visible in the app history area. Typical use: energy analytics dashboards, customer segmentation by usage behavior, and budget alerting rules for high-variance months.

3) Outage and service request tracking

Normalize outage reports, protocol numbers, timestamps, and lifecycle updates. Typical use: service desks that need a single timeline across utility incidents, internal tickets, and customer notifications.

4) Reconnection and ownership transfer workflow API

Integrate request submission and status checks for reconnection and titularity changes. Typical use: property management platforms that must prove utility activation state before handover or move-in processing.

5) Debt negotiation and installment flow integration

Model negotiation proposals, installment options, and acceptance events where available in authorized flows. Typical use: collections operations and customer-success teams that need programmatic debt resolution tracking.

6) Meter reading declaration and validation API

Capture declared readings, reference period, and validation outcomes. Typical use: exception management and auditing when billing disputes require historical reading evidence.

Snippet 1 - Authorized login/session exchange

POST /api/v1/energisa/session/login
Content-Type: application/json

{
  "cpf_cnpj": "12345678901",
  "password_or_otp": "***",
  "device_id": "android-a1b2c3"
}

Response 200
{
  "session_token": "eyJ...",
  "expires_in": 3600,
  "customer_id": "cus_93821",
  "linked_installations": 3
}

Implementation note: persist only encrypted session artifacts and rotate refresh credentials according to project retention policy.

Snippet 2 - Invoice and statement retrieval

GET /api/v1/energisa/invoices?installation_id=INST-44&from=2025-01&to=2025-06
Authorization: Bearer <SESSION_TOKEN>

Response 200
{
  "items": [
    {
      "invoice_id": "inv_2025_05",
      "due_date": "2025-05-18",
      "amount": 286.74,
      "status": "paid",
      "barcode": "8364...",
      "pix_copy_paste": "000201..."
    }
  ]
}

Error handling pattern: return deterministic codes like INSTALLATION_NOT_FOUND, UNAUTHORIZED_SCOPE, and UPSTREAM_TIMEOUT for reliable retries.

Snippet 3 - Outage/request webhook

POST /webhooks/energisa/request-status
X-Signature: sha256=ab12...

{
  "request_id": "req_7781",
  "type": "outage_report",
  "status": "in_progress",
  "updated_at": "2026-04-16T11:25:43Z",
  "protocol_number": "20260416-55671"
}

Response: 202 Accepted

Recommended architecture: verify signature, store raw payload, then publish normalized events to queue topics used by CRM and alerting systems.

Compliance and privacy

For Brazil-focused utility integrations, LGPD (Lei Geral de Protecao de Dados) is the baseline legal framework for personal data processing. CPF/CNPJ identifiers, account metadata, billing records, and service-request logs must follow legal basis, purpose limitation, and data subject rights obligations.

When projects involve payment references or debt settlement information, teams usually pair LGPD controls with finance-grade controls such as strict access logging, least-privilege keys, retention windows, and incident response procedures. Our implementation documentation includes consent tracking recommendations and data minimization decisions so the integration remains auditable.

Data flow and architecture

Typical pipeline: Client app session layer -> Ingestion/API worker -> Normalized storage -> Business API or webhook output. In practice, this means a connector acquires consented account data, maps records into a stable schema, stores immutable event logs, and serves downstream systems through secured endpoints.

For higher-volume environments, we add a queue between ingestion and storage to isolate upstream latency from analytics workloads, plus idempotency keys on invoice and request events.

Cemig Atende

Commonly used in Minas Gerais for second-copy bills, PIX-ready payment flows, and outage communication. Teams integrating both Cemig Atende and Energisa On usually want a unified utility invoice export API.

Neoenergia Brasilia

Provides invoice duplication, reconnection requests, and outage reports in the Federal District context. Similar integration projects often standardize service-request status fields across distributors.

Copel

Parana-focused utility app with billing access and outage-related customer actions. Organizations with operations in multiple states often consolidate Copel and Energisa data into one compliance-aware reporting layer.

Enel Sao Paulo

Supports outage reporting and second-copy account journeys at high urban density. Integrators frequently map Enel and Energisa account events to common SLA dashboards.

CPFL Energia

Offers app-based invoice access and consumption monitoring. Data teams that already ingest CPFL consumption history often request equivalent Energisa On consumption endpoints for cross-provider benchmarking.

Equatorial Energia

Known for invoice history and service management features across several states. Multi-region utility operators use shared schema design to compare payment behavior and consumption trends between Equatorial and Energisa territories.

Light Clientes

Widely referenced for second-copy and customer support channels in Rio de Janeiro. Integrations touching both platforms usually prioritize common identity, invoice, and outage message contracts.

About our studio

We are a technical service studio focused on app interface integration and authorized API implementation for global clients. Our background combines mobile engineering, fintech data operations, reverse engineering for protocol understanding, and production API delivery in regulated environments.

Engagement starts with only two inputs from the client: target app name and required outcomes. From there, we deliver protocol analysis, interface refactoring recommendations, third-party connector implementation, automated data scripts, and complete interface documentation ready for developer teams.

• Android and iOS integration coverage with reproducible test plans.
• Source-code delivery model from $300 with documentation and runnable examples.
• Pay-per-call hosted API model for teams preferring usage-based cost control.
• Workflow transparency from requirement confirmation to acceptance testing.

Contact information

To request an Energisa On API integration proposal, share your target workflows (for example: invoice export, outage synchronization, reconnection tracking, or debt negotiation analytics) and your preferred delivery model.

Go to contact page

We respond with scope, timeline, and a clear list of required inputs before implementation starts.

Deliverables checklist

• Integration architecture note and endpoint catalog
• Authorization/session flow specification
• Runnable API source code (selected language stack)
• Automated extraction scripts and sample payloads
• Error code matrix and retry guidance
• Interface documentation and test cases

Workflow

1. Requirement mapping: business outcomes, required fields, target systems.
2. Protocol analysis: authenticated flows, data object mapping, rate behavior.
3. Build phase: endpoint implementation, schema normalization, security controls.
4. Validation: integration tests, edge-case handling, payload consistency checks.
5. Delivery: source code, docs, and handover support for deployment.

FAQ

What do we need to start?
App name, your use cases, required data fields, and preferred delivery model.

Can this support both analytics and operations?
Yes. We commonly split outputs into event streams for operations and curated datasets for BI/reporting.

Do you provide compliance guidance?
Yes. We include implementation notes aligned with LGPD-oriented data handling and access control practices.