Everon offers a number of APIs to help you to create, manage, and maintain your EV charging infrastructure. Depending on your needs, you can use a single API or combine them to enable more use cases:

Everon API basics

Everon APIs are RESTful and follow the OpenAPI specification. You can download our API specifications through our developer portal. This makes it easy for you to either run an interactive user interface or to generate high level clients for various programming languages, depending on your needs.

Path structures

All of our APIs follow the same URL pattern: https://api.everon.io/<endpoint>/<version>/<query>. For example: https://api.everon.io/billing/v1/transactions


Our APIs allow the common HTTP methods. The available methods differ depending on the API.




Retrieve requested information.


Partially update a resource.


Create a resource.


Update a resource.


Delete a resource.

Response codes

Our API responses follow standard HTTP status codes.


The request was processed successfully. 

400The request couldn't be processed because of incorrect or missing parameters.
401The request was unauthorized.
403The request wasn't allowed due to missing permissions.
404The requested resource doesn't exist.
5xxThere was an error on Everon's side.

Standard formats

To ensure our APIs are consistent, we follow a number of standard formats.



TimestampsTimestamps are in Coordinated Universal Time (UTC) and according to ISO 8601: YYYY-MM-DD'T'HH:MM:SS'Z'
Unique identifiers (UUIDs)

Everon uses version 4 universal unique identifiers (UUIDs), which are randomly generated 128-bit numbers. For example: 9b00760c-90c0-4799-a460-da3e0fb7d2ad.

All resources in your tenant have a UUID. If you need a UUID for your request that you can't get using an API call, it appears in the URL when you navigate to the resource in your tenant platform.