Software Builders & APIs

Build energy products without building the connector burden.

EDX gives software teams one normalized API for solar, batteries, EV chargers, smart meters, and project telemetry, so engineering time goes into product logic instead of hardware-specific integration debt.

Book a builder walkthrough Explore the platform

REST + WebSocket ESDL-aligned model Scoped API keys

developer preview

GET /projects/{id}/devices

GET /devices/{id}/timeseries?from=&to=&interval=

WS /stream/devices/{id}

{
  "device_id": "meter-019",
  "type": "smart_meter",
  "data_type": "electricity",
  "health_score": 0.95
}

One schema for different hardware types, with quality signals and governance built in.

The Problem

Every new hardware brand becomes another line item in your roadmap debt.

Software teams want to ship dashboards, automations, and customer-facing workflows. Instead, every new meter, inverter, charger, or site setup keeps pulling engineering time back into auth edge cases, payload translation, and connector maintenance.

Fragmented APIs Auth models, payloads, webhook behavior, and failure modes all vary by device brand and protocol.

Maintenance tax Firmware changes, model-specific edge cases, and new customer hardware requests slowly turn your team into a connector maintenance squad.

Partner complexity When data needs to reach customers, partners, or internal teams, access control and traceability become product requirements.

Why Teams Choose EDX

One integration surface for the energy data your product actually needs.

Integration surface

Normalize once, then build product logic on top.

Capability Without EDX With EDX Partner ready

Live and batch access Vendor specific Unified Scoped keys

Object model Payload drift Shared schema Reusable

Telemetry trust Opaque Health scored Auditable

What changes

Your team stops rebuilding the connector layer for every deployment.

Single surfaceREST for historical queries and WebSocket for live flows inside one permission model.

Unified

Stable modelProjects, buildings, devices, and datapoints stay queryable even when the hardware mix changes.

Structured

Controlled sharingExpose only the sites, devices, and streams each partner should see, with traceability built in.

Governed

Supported Device Surface

Built for the hardware mix your customers already run.

Inputs

Smart meters

Solar inverters

Batteries

EV charging

Heat pumps

EDX Connector and governance layer

REST + WebSocket Health signals Reusable connectors

Outputs

EMS dashboard

Optimization engine

Customer portal

Analytics stack

Partner API

Absorb hardware fragmentationThe connector layer takes the variability so your roadmap does not have to mirror every vendor portal.

Support real product logicDashboards, automations, optimization, and customer-facing views consume one coherent access layer.

Stay partner-readyShare controlled access with customers and downstream teams without duplicating the platform surface.

Developer Workflow

How software teams usually use EDX inside the stack.

01

Connect the required hardware sources

Map the device landscape once instead of rebuilding a new integration layer for each customer or deployment.

02

Build product logic on the normalized API

Dashboards, automations, optimization, analytics, and customer-facing views consume one coherent data model.

03

Share access with customers or partners

Use scoped keys and governance controls to expose the right data without introducing platform sprawl.

Related Paths

Where teams usually go next.

Platform

Want to see how EDX fits your current stack?

We’ll walk through your device mix, API expectations, partner-sharing needs, and what a clean integration path would look like for your product team.