API Introduction

Why eDRV?

eDRV allows you to connect any Open Charge Point Protocol (OCPP) compatible EV charge station to your application without spending weeks and months building and maintaining your own messaging stack.

eDRV Platform Introduction

Network Architecture - M2M API

However the eDRV cloud platform goes much further than simply wrapping a RESTful API around OCPP. The platform adds an additional layer of Charging Intelligence ensuring your engineering team is focussing on driver experience rather than building tooling around EV charging. For e.g. eDRV ensures that a driver is automatically cutoff when they hit an energy consumption threshold set by the developer.

eDRV also allows you to accept payments for EV charging via an API. See How to use Payment Links and Introduction to Wallets.

Server Side REST API

eDRV is a Machine-to-Machine, server side API. Developers are expected to send requests to eDRV cloud on behalf of your client facing applications and users/drivers.

The eDRV API is grounded within REST and HTTP allowing you to use any HTTP client or programming language. All requests and responses are JSON formatted and use standard HTTP response codes, authentication, and verbs.


Calling the API directly from Client Devices

Using your eDRV APIs directly in a client application is a security risk and is prohibited. eDRV is a server side only API and thus we do not have any mobile / client device SDKs.

Supported Protocols

OCPP 1.6 JAC & DC Charge StationsOCPP 1.6J Specification
OCPP 2.0.1

*Core use cases only
AC & DC Charge StationsOCPP 2.0.1 Specification

What’s Next

Check out our Quickstart guide next.