Solar panels, EV chargers, HVAC, smart appliances — Derapi normalizes every vendor protocol into a single REST API. Stop rebuilding integrations. Ship the product.
Five core capabilities that remove the integration layer between your application and the hardware fleet it manages.
Every DER device type returns the same normalized JSON structure
Derapi defines an open device taxonomy with standardized fields for each DER category. Solar inverters return output_kw, lifetime_kwh, grid_connection_status. Battery systems return state_of_charge, charge_power_kw, available_capacity_kwh. Developers write against one schema that works across SolarEdge, Enphase, Tesla Powerwall, and 40+ additional vendors. When a vendor updates their API, Derapi updates the adapter.
IEEE 2030.5, OpenADR 2.0, OCPP 1.6/2.0, Modbus, and proprietary REST — all handled server-side
Derapi's protocol adapters cover the full range of DER communication standards: IEEE 2030.5 for utility-grade solar and storage, OpenADR 2.0a/b for demand response signals, OCPP 1.6 and 2.0 for EV charging station management, Modbus/TCP for industrial inverters and commercial HVAC. Developers access all protocols through Derapi's unified REST endpoint — no protocol-specific SDK required.
Device-vendor OAuth tokens and API keys stored encrypted — your app never holds third-party credentials
When a developer onboards a device fleet through Derapi, vendor credentials are stored in Derapi's encrypted credential vault using AES-256 at rest and TLS 1.3 in transit. The developer's application passes only a Derapi device ID in API calls. Vault entries rotate automatically when vendor tokens expire, and audit logs record every credential access.
Subscribe to device state changes and grid signals with webhooks or WebSocket streams — no polling required
Derapi's event engine maintains persistent connections to supported DER vendors and normalizes device events into a uniform event schema. Developers subscribe to event types via a simple API call and receive normalized event payloads via webhook or WebSocket. The engine handles fan-out to multiple subscriber endpoints, deduplication of duplicate vendor events, and guaranteed delivery with a 72-hour retry window.
Full API sandbox with simulated DER device fleets — test demand-response scenarios without hardware
Derapi's sandbox mirrors the production API surface with a fleet of simulated devices spanning solar arrays, residential storage, EV charging stations, and smart thermostats. Developers can inject synthetic telemetry data, trigger simulated grid events, and test command sequences against virtual device behavior models. The sandbox is fully isolated from production device networks and maintains state between API calls within a 30-day session window.
Three steps to start reading and controlling DER hardware across vendors.
Request access through the Derapi portal. Receive a sandbox API key immediately and a production key after account verification. Onboard your device fleet by connecting vendor credentials through the secure vault flow.
Use Derapi's REST endpoint to read telemetry, send commands, or subscribe to events. One endpoint, one authentication scheme, one normalized JSON schema — regardless of the underlying device vendor or communication protocol.
Your application talks to Derapi; Derapi handles every vendor's authentication, protocol translation, and error handling. Add new device vendors to your supported fleet without touching your application code.
Without a shared abstraction layer, every new DER hardware vendor means a new bespoke integration that consumes weeks of engineering time. A unified API schema changes that — one data model for every device type, regardless of manufacturer.
Read more
OCPP 2.0 is more than a version bump — it introduces mandatory TLS security profiles, a hierarchical device model, and a revised transaction lifecycle that breaks code ported directly from 1.6. Here is what changed and where teams get stuck.
Read more
OpenADR's VEN/VTN message model, registration flow, event lifecycle, and telemetry reporting requirements — explained for developers building demand response software from scratch.
Read moreGet a Derapi API key, access the sandbox, and have your first normalized device telemetry call running within the hour.