Build with Easee

Take control of Easee chargers and equalizers through multiple integration pathways. Pick the path that matches what you are building and we will take you to the right docs.

Which docs do you need?

The difference comes down to whose chargers you want to control: your own, or other people's.

Partner dev docs

For operators, CPOs and software providers

Offer smart charging, access control or other services to many site owners. Partner integrations act as an operator and can be offered to multiple customers.

Explore partner docs

Home user dev docs

For home owners, local home devices and small business owners

Control your own chargers with Direct OCPP or our public API in combination with signalR, without needing to set up a partner integration. Ideal for home automation, HEMS and personal projects.

Open the API reference

Not sure which one is yours?

A quick comparison of the two integration types.

	Partner	Home user
Whose chargers	Chargers belonging to your customers, managed by serial number	Chargers you own or have access to
Commercial use	Yes, you can offer a service to other site owners	No, the public API cannot be used commercially or monetised
Customer data	You run your own customer database, RFID keys and so on	Not applicable, access is limited to a single user's sites
Responsibility	You take responsibility for the integration and how it controls devices	You are responsible for the integration and for storing credentials safely
Support	Easee helps you get started, then you own the product	Self-serve support through developer documentation

Note: Easee user credentials must not be used by a third party to gain access to or control a charger. If you are building something for other people, you need a partner integration.

Jump straight to

Shared resources for both audiences.

API referenceEvery endpoint, in one place Observation IDsCharger and equalizer data points Error codesEnumerations and what they mean ChangelogWhat has changed and when