How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
ev.energy

ev.energy EVS Es API

Endpoints for interacting with EVSEs.

Documentation Provider Profile APIs.io OpenAPI GitHub

ev.energy EVS Es API is one of 25 APIs that ev.energy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include EVSEs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 25 operations across 23 paths, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against 2 base URLs: https://api.ev.energy/v2, https://api-staging.ev.energy/v2.

25 operations 23 paths 32 schemas 1 DELETE20 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.ev.energy/v2
Authentication
OAuth 2.0
Contact
ev.energy developers
License
Proprietary
Resource Areas
1

Authentication & Security 1

ev.energy EVS Es API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the clientCredentials and authorizationCode flows, exposing 35 scopes. By default, every request must be authenticated.

Paths & Operations 25

Across 23 paths, the API surfaces 25 operations — 1 DELETE, 20 GET, 1 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

EVSEs 25

Endpoints for interacting with EVSEs.

GET
/evse_compatibility/check
Check EVSE model compatibility in a country
get-evse_compatibility-check 6 params → 200400401404405406
GET
/evses
List EVSEs
get-evses 7 params → 200400401403406429
GET
/evses/{evse_id}
Retrieve an EVSE
get-evses-evse_id 3 params → 200400401403404406429
PATCH
/evses/{evse_id}
Update an EVSE
patch-evses-evse_id 3 params body → 200400401403404406429
DELETE
/evses/{evse_id}
Decommission an EVSE
delete-evses-evse_id 2 params → 204401403404406429
GET
/evse_models
List EVSE models
get-evse_models 8 params → 200400401403406429
GET
/evse_models/{evse_model_id}
Retrieve an EVSE model
get-evse_models-evse_model_id 3 params → 200400401403404406429
GET
/evse_makes
List EVSE makes
get-evse_makes 6 params → 200400401403406429
GET
/evse_makes/{evse_make_id}
Retrieve an EVSE make
get-evse_makes-evse_make_id 2 params → 200400401403404406429
GET
/evses/{evse_id}/status_logs
List status logs for an EVSE
get-evses-evse_id-status_logs 8 params → 200400401403404406429
GET
/evses/{evse_id}/status_logs/{sampled_at}
Retrieve a status log for an EVSE
get-evses-evse_id-status_logs-timestamp 4 params → 200400401403404406429
GET
/evses/{evse_id}/command_logs
List command logs for an EVSE
get-evses-evse_id-command_logs 8 params → 200400401403404406429
GET
/evses/{evse_id}/command_logs/{logged_at}
Retrieve a command log for an EVSE
get-evses-evse_id-command_logs-timestamp 4 params → 200400401403404406429
GET
/evses/{evse_id}/error_logs
List API error logs for an EVSE
get-evses-evse_id-error_logs 8 params → 200400401403404406429
GET
/evses/{evse_id}/error_logs/{sampled_at}
Retrieve a specific API error log for an EVSE
get-evses-evse_id-error_logs-timestamp 4 params → 200400401403404406429
GET
/evses/{evse_id}/ocpp_logs
List OCPP logs for an EVSE
get-evses-evse_id-ocpp_logs 13 params → 200400401403404406429
GET
/evses/{evse_id}/ocpp_logs/{sampled_at}
Retrieve an OCPP log for an EVSE
get-evses-evse_id-ocpp_logs-timestamp 4 params → 200400401403404406429
GET
/evses/{evse_id}/vpp_modes
Get VPP modes for an EVSE
get-evses-evse_id-vpp_modes 2 params → 200400401403404406429
GET
/evses/{evse_id}/connectivity
Get connectivity information for an EVSE
get-evses-evse_id-connectivity 3 params → 200400401403404406429
POST
/evses/{evse_id}/reconnect
Create EVSE reconnection URL
post-evses-evse_id-reconnect 2 params body → 201400401403404406429
GET
/evse_firmware_versions
List EVSE firmware versions
get-evse_firmware_versions 4 params → 200400401403406429
GET
/evse_firmware_versions/{evse_firmware_version_id}
Retrieve an EVSE firmware version
get-evse_firmware_versions-evse_firmware_version_id 2 params → 200400401403404406429
GET
/evse_onboarding
Initiate EVSE onboarding
get-evse_onboarding 6 params → 200302400404
POST
/evse_onboarding/import
Import an EVSE by serial number
post-evse_onboarding-import 2 params body → 201400401403404406422429
POST
/evse_waitlist
Add user to the EVSE waitlist
post-evse_waitlist 3 params body → 201400405406429

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are EVSEStatusLog (18 properties), Notification (13 properties), TariffBase (13 properties), EVSE (11 properties). Each schema is shown below with its type and property counts.

Supplier
object
An energy company who supplies electricity tariffs.
5 properties 4 required
EVSEAPIErrorLog
object
Records an error that occurred when attempting to communicate with an EVSE's hardware API.
10 properties
EVSEFirmwareVersion
object
A specific firmware release available for one or more EVSE models.
6 properties 6 required
EVSEConnectivity
object
Connectivity snapshot for an EVSE including signal strength, SIM data, firmware version, and connection reliability.
8 properties 8 required
CTClamp
object
A CT (Current Transformer) clamp used to measure grid current, typically for solar charging logic.
4 properties
EVSEOCPPLog
object
Records an OCPP message sent to or received from an EVSE.
8 properties
Times
object
Defines a period of time.
2 properties
EVSEWaitlistRequest
object
Request body for POST /evsewaitlist. Device identification fields are mutually constrained: supply exactly one of (evsemodelid) or (both evsemakename and evsem…
5 properties 1 required
DailyPrices
object
Information about the tariff's prices for different parts of the day.
3 properties 1 required
EVSEMake
object
A resource representing a manufacturer of EVSEs.
8 properties 3 required
Tariff
Note: dailyprices and type are only available under contract. Please reach out to your account manager to find out more.
EVSESite
object
Represents a place with one or more EVSEs installed which can be accessed by multiple users.
6 properties 4 required
EVSEOCPPCallResponse
object
The response to an OCPP call message.
4 properties
EVSEModel
object
A resource representing a model of EVSEs.
6 properties 3 required
Location
object
Location model for charging locations. Address validation: Address fields are optional as a group, but each field independently triggers the requirement. If an…
9 properties
EVSEImportRequest
object
Request body for POST /evseonboarding/import. The backend uses the authenticated user's email (and secondaryemail if set on the profile) to look up the device…
2 properties 2 required
EVSECompatibilityCheckResult
object
Compatibility verdict for an (EVSEModel, country) pair. Returned by GET /evsecompatibility/check.
3 properties 3 required
EVSEReconnectionUrl
object
A URL for a user to re-authenticate their EVSE.
1 property
CountryCode
string
ISO 3166-1 2 letter Country Codes.
EVSEStatusLog
object
Records the state of an EVSE at a particular point in time.
18 properties
LocationDetail
Extra fields only included when a single location is requested but omitted when locations are listed.
PriceSummary
object
A single price for a certain time range.
2 properties
EVSEWaitlistResponse
object
Response body for POST /evsewaitlist. Echoes just the new entry's uid; no url is returned because the endpoint exposes no retrieve action (privacy by design —…
1 property 1 required
RFC9457ProblemDetail
object
6 properties 2 required
Notification
object
Something that the user should be informed about.
13 properties 11 required
EVSECommandLog
object
Records a command that was sent to an EVSE.
8 properties
EVSE
object
A resource that represents a single, physical piece of hardware for supplying electricity to an electric vehicle.
11 properties 3 required
VPPModes
object
VPP (Virtual Power Plant) mode capabilities indicating which control modes are supported by the resource.
4 properties 4 required
TariffBase
object
Core tariff properties shared by Tariff and expanded schedulertariff. Note: dailyprices and type are only available under contract. Please reach out to your ac…
13 properties 5 required
User
object
A resource that represents an individual user in the ev.energy system.
9 properties 2 required
LatLong
object
Coordinates model used for locations.
2 properties 2 required
EVSEOnboardingJsonResponse
object
JSON payload returned by GET /evseonboarding?responsetype=json. Carries the absolute Start-wrapper URL.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ev-energy-evses-api-openapi.yml Raw ↑

Other APIs ev.energy publishes across the network.

ev.energy Auth API
AE Profile APIs.io
ev.energy Boundary Meters API
AE Profile APIs.io
ev.energy Carbon API
AE Profile APIs.io
ev.energy Charging Sessions API
AE Profile APIs.io
ev.energy CT Clamps API
AE Profile APIs.io
ev.energy Grid API
AE Profile APIs.io
ev.energy HEM Systems API
AE Profile APIs.io
ev.energy Home Batteries API
AE Profile APIs.io
ev.energy Notifications API
AE Profile APIs.io
ev.energy Programs API
AE Profile APIs.io
ev.energy Rebates API
AE Profile APIs.io
ev.energy Reference Data API
AE Profile APIs.io
#EVSEs
← Back to E APIs
API Details
ID
ev-energy:ev-energy-evses-api
Base URL
https://api.ev.energy/v2
Docs
https://developers.ev.energy/ev.energy-api-v2
Provider
ev.energy
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=ev-energy-evses-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/ev-energy-evses-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of ev.energy EVS Es API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.