Automate eDRV

What eDRV is

edrv.io API Documentation

What HumDay can do in eDRV

28 documented operations change something in eDRV.

• POSTCreate a new charge station/v1/chargestations
• POSTCreate a new token/v1/tokens
• POSTCreate a new driver/v1/drivers
• POSTCreate a new location/v1/locations
• POSTCreate a new connector/v1/connectors
• POSTCreate connector with parameters/v1/configurations
• DELETEDelete a smart charging schedule/v1/commands/chargingschedule
• DELETEUse to delete a charge station/v1/chargestations/{id}
• PATCHUpdate a charge station's data/v1/chargestations/{id}
• POSTChange charge/v1/vehicles/{id}/charge
• POSTUse to request a reset command./v1/commands/reset
• POSTUse to request a reserve command./v1/commands/reserve
• POSTUse to request a remote stop command./v1/commands/remotestop
• POSTUse to request a remote start command./v1/commands/remotestart
• POSTUse to request an unlock command for a connector./v1/commands/unlockconnector
• POSTSet one of charging power or current of a specific chargestation connector/v1/commands/chargingschedule
• POSTUse to request a delete an existing reservation./v1/commands/cancelreservation
• DELETEUse to delete a token/v1/tokens/{id}
• PATCHUpdate a token/v1/tokens/{id}
• DELETEDelete a driver/v1/drivers/{id}
• PATCHUpdate a driver's data/v1/drivers/{id}
• DELETEDelete a location/v1/location/{id}
• PATCHUpdate a location's data/v1/location/{id}
• DELETEDelete a connector/v1/connectors/{id}
• PATCHUpdate a connector's data/v1/connectors/{id}
• PATCHUse to request a update an existing reservation./v1/reservations/{id}
• PATCHUpdate an organization's data/v1/organizations/{id}
• PATCHUpdate config variables for a chargestation/v1/commands/{id}/variables

What HumDay can read from eDRV

These are the operations a schedule or a trigger can watch.

• GETList all Chargestations/v1/chargestations
• GETList tokens/v1/tokens
• GETList all drivers/v1/drivers
• GETList all vehicles/v1/vehicles
• GETList connectors/v1/connectors
• GETGet a list of transactions/v1/transactions
• GETList connectors for a chargestation/v1/chargestations/{id}/connectors
• GETGet a single charge station's data/v1/chargestations/{id}
• GETGet Commands data/v1/commands
• GETUse to request a Websockets handshake/v1/realtime
• GETGet Locations data/v1/locations
• GETGet Reservations data/v1/reservations
• GETGet an array of all Organizations/v1/organizations
• GETGet Configurations data/v1/configurations
• GETGet a vehicle's charge/v1/vehicles/{id}/charge
• GETGet a charge station's config variables/v1/commands/{id}/variables
• GETGet a single token's data/v1/tokens/{id}
• GETGet a driver's data/v1/drivers/{id}
• GETGet a location's data/v1/location/{id}
• GETGet a vehicle's data/v1/vehicles/{id}
• GETGet a connector/v1/connectors/{id}
• GETGet one reservation data/v1/reservations/{id}
• GETGet a specific transaction/v1/transactions/{id}
• GETGet one organization's data by id/v1/organizations/{id}
• GETGet one Configuration data/v1/configurations/{id}
• GETGet a vehicle's battery/v1/vehicles/{id}/battery
• GETGet a specific transaction's cost/v1/transactions/{id}/cost
• GETGet a vehicle's location/v1/vehicles/{id}/location
• GETGet a vehicle's odometer/v1/vehicles/{id}/odometer

How automating eDRV works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live eDRV account.
4. Grant access, then go live. You approve the specific eDRV operations it may use — and only those.

Automate eDRV with these

• Monarchinitiative BioLink164 operations
• UniCourt Enterprise158 operations
• OSF APIv2 Documentation156 operations
• IllumiDesk143 operations
• Figshare136 operations
• MCW Rat Genome Database100 operations
• U.S. EPA Enforcement and Compliance History Online (ECHO) Detailed Facility Report (DFR)94 operations
• OpenFEC91 operations
• NBA Stats83 operations
• Thebluealliance The Blue Alliance65 operations
• Collegefootballdata College Football Data51 operations
• Dnd5eapi D&D 5e47 operations

Categories

• Open data
• Transport
• Location

Questions about eDRV automation

Can HumDay connect to eDRV?

Yes. HumDay reads eDRV's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 57 operations are documented.

Do I need to write code to automate eDRV?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your eDRV account.

What can HumDay do in eDRV?

28 of the 57 documented operations change something in eDRV, and 29 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my eDRV account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to eDRV is held behind that approval.

Where this came from

The operations above are read from a published API description for eDRV at developers.edrv.io/openapi/5f15c43c87b0d6001ea97414. Descriptions are the provider’s own words, not ours. Last published 2020-12-30.