eDRV API

Name: eDRV API API
Brand: eDRV API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTDevice Managementoauth257 EndpointsREST

For Agents

Manage EV charging stations, drivers, reservations, and live charging sessions across an eDRV-powered charging network.

Quickstart

Get started with eDRV API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"remotely start an EV charging session"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with eDRV API API.

Provision and configure charge stations and their connectors across an EV charging network

Send remote-start, remote-stop, reset, and unlock-connector commands to stations in the field

Schedule reservations for chargers and cancel them through structured command endpoints

Manage drivers and the RFID or app authorisation tokens that grant them charging access

GET STARTED

Start building with eDRV API API

Explore with Jentic

View OpenAPI Document

Use for: I need to remotely start a charging session on a specific charge station, Send a remote-stop command to end a charging session, List all charge stations in my organisation, Find the current battery state of charge for a connected vehicle

Not supported: Does not handle electricity tariff calculation, end-customer billing, or hardware firmware updates — use for managing charge stations, sessions, drivers, reservations, and EV telemetry only.

Jentic publishes the only available OpenAPI document for eDRV API, keeping it validated and agent-ready.

eDRV is a managed back-end for electric-vehicle (EV) charging networks. The v1 API exposes 57 endpoints that let operators provision charge stations, configure connectors, control charging sessions through remote-start and remote-stop commands, manage drivers and authorisation tokens, model locations and organisations, run reservations, and pull realtime telemetry, transactions, and statistics. It also includes vehicle telematics endpoints for battery, charge state, location, and odometer.

Use Cases

Patterns agents use eDRV API API for, with concrete tasks.

★ Fleet charging operations console

A fleet operator runs an internal console that needs to see live charger availability, dispatch drivers, and start or stop charging sessions remotely. The eDRV API supplies the realtime status, the remote command endpoints, and the transactions feed that the console needs. Operators can resolve stuck sessions in seconds rather than dispatching a technician.

Call POST /v1/commands/remotestart with the chargestationId and connectorId for the target driver, then poll /v1/realtime to confirm the session began.

Driver-facing charging app

A consumer app lets EV drivers find a charger, reserve it, and start the session from their phone. The app uses eDRV's locations and chargestations endpoints to populate the map, the reservations endpoints to hold a connector for the driver, and the remote-start command to begin charging once the driver plugs in. The 57-endpoint surface covers the full driver journey end to end.

Reserve a connector via POST /v1/commands/reserve, then call POST /v1/commands/remotestart when the driver plugs in, and report transaction status from /v1/transactions.

Vehicle telematics enrichment

A logistics platform pairs EV telematics with route planning. The eDRV vehicle endpoints expose battery state-of-charge, charge state, location, and odometer for connected vehicles, so the planner can decide which vehicles need charging stops on a given route. The data flows alongside the network's charge-station availability for end-to-end EV operations.

Call GET /v1/vehicles/{id}/battery for each vehicle on a planned route and return those with state-of-charge below the configured threshold.

AI agent for charge-network support

An operations agent triages support cases for a charging network: stuck sessions, unresponsive connectors, or driver tokens that fail to authorise. Through Jentic, the agent searches by intent, loads the right eDRV operation, and executes resets, unlocks, or token lookups without the engineer needing to memorise the 57-endpoint API.

Search Jentic for 'reset a charge station' to load POST /v1/commands/reset, then execute it for the affected stationId and confirm via /v1/realtime.

Key Endpoints

57 endpoints — edrv is a managed back-end for electric-vehicle (ev) charging networks.

METHOD

PATH

DESCRIPTION

GET

/v1/chargestations

List charge stations

POST

/v1/commands/remotestart

Remotely start a charging session

POST

/v1/commands/remotestop

Remotely stop a charging session

POST

/v1/commands/reserve

Reserve a connector

GET

/v1/transactions

List charging transactions

GET

/v1/vehicles/{id}/battery

Get vehicle battery state of charge

GET

/v1/vehicles/{id}/location

Get vehicle location

GET

/v1/chargestations

List charge stations

POST

/v1/commands/remotestart

Remotely start a charging session

POST

/v1/commands/remotestop

Remotely stop a charging session

POST

/v1/commands/reserve

Reserve a connector

GET

/v1/transactions

List charging transactions

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

eDRV OAuth 2.0 credentials are stored encrypted in the Jentic vault (MAXsystem). Jentic performs the implicit-flow exchange, manages scope-limited tokens, and injects them at execution time so agents never see the raw secrets.

Intent-based discovery

Agents search Jentic by intent — 'remotely start a charge', 'list charge stations', 'reserve a connector' — and Jentic returns the matching eDRV operation with its input schema, mapping intents to the right entry across the 57-endpoint surface.

Time to first call

Direct integration: 5-10 days to handle OAuth, scope management, command flows, and realtime polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Twilio API

Twilio sends SMS notifications to drivers when a charging session starts, completes, or fails.

Pair with eDRV when the operations agent needs to message drivers or operators about charging events.

Complementary

Stripe API

Stripe handles per-session billing for charging transactions reported by eDRV.

Use Stripe alongside eDRV transactions to charge drivers for energy delivered, with Stripe Customers and PaymentIntents tied to eDRV driver IDs.

Complementary

Auth0 API

Auth0 manages end-user identity for driver-facing apps that consume the eDRV API.

Use Auth0 for driver authentication in a consumer EV app while eDRV handles charging operations.

FAQs

Specific to using eDRV API API through Jentic.

What authentication does the eDRV API use?

eDRV uses OAuth 2.0 with the implicit flow against https://auth.edrv.io/authorize and per-resource scopes such as read:chargestations, write:commands/remotestart, and read:transactions. Jentic stores the credentials encrypted, performs the OAuth exchange, and injects scoped tokens at execution time.

Can I remotely start and stop a charging session with the eDRV API?

Yes. POST /v1/commands/remotestart begins a session and POST /v1/commands/remotestop ends it. There are also command endpoints for reset, unlockconnector, reserve, and cancelreservation.

How do I read the live status of a charge station?

Use the realtime endpoints under /v1/realtime to pull live status across stations and connectors, alongside GET /v1/chargestations and GET /v1/chargestations/{id}/connectors for configuration data.

Can I see a connected vehicle's battery state through this API?

Yes. GET /v1/vehicles/{id}/battery returns battery state for a connected EV, and the related endpoints expose charge state, location, and odometer for the same vehicle.

What are the rate limits for the eDRV API?

Rate limits are not declared in the OpenAPI spec and are typically agreed per network with eDRV. For the realtime and command endpoints in particular, follow eDRV's guidance and use webhooks or event subscriptions where available rather than tight polling.

How do I send a remote-start command through Jentic?

Install the SDK with pip install jentic, search Jentic for 'remotely start an EV charging session', load the schema for POST /v1/commands/remotestart, and execute with the chargestationId and connectorId. Jentic handles the OAuth exchange and returns the command result to the agent.