Automate Enode
HumDay reads Enode’s own published API description and derives 28 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Enode is
Download [OpenAPI 3.0 Specification](/OpenAPI-Enode-v1.4.0.json) Download [Postman Collection](/Postman-Enode-v1.4.0.json) The Enode API is designed to make smart charging applications easy to develop. We provide an abstraction layer that reduces the complexity when extracting vehicle data and sending commands to vehicles from a variety of manufacturers. The API has a RESTful architecture and util
API host: api.test.enode.io
What HumDay can do in Enode
13 documented operations change something in Enode.
- DELETEUnlink User
/users/{userId} - POSTLink User
/users/{userId}/link - POSTCreate Charging Location
/charging-locations - DELETEDeauthorize User
/users/{userId}/authorization - PUTUpdate Firehose Webhook
/webhooks/firehose - POSTTest Firehose Webhook
/webhooks/firehose/test - DELETEDelete Charging Location
/charging-locations/{chargingLocationId} - PUTUpdate Charging Location
/charging-locations/{chargingLocationId} - DELETEDisconnect Vendor
/me/vendors/{vendor} - POSTStart Watching Vehicle
/vehicles/{vehicleId}/watch - POSTControl Charging
/chargers/{chargerId}/charging - POSTStart / Stop Charging
/vehicles/{vehicleId}/charging - PUTUpdate Vehicle Smart Charging Policy
/vehicles/{vehicleId}/smart-charging-policy
What HumDay can read from Enode
These are the operations a schedule or a trigger can watch.
- GETGet My User
/me - GETList Chargers
/chargers - GETList Vehicles
/vehicles - GETList Charging Locations
/charging-locations - GETGet User Charging Statistics
/statistics/charging - GETGet Vehicle Charge State
/vehicles/{vehicleId}/charge-state - GETCheck Service Readiness
/health/ready - GETCheck Available Vendors
/health/vendors - GETGet Charger
/chargers/{chargerId} - GETGet Vehicle
/vehicles/{vehicleId} - GETGet Charging Location
/charging-locations/{chargingLocationId} - GETGet Vehicle Location
/vehicles/{vehicleId}/location - GETGet Vehicle Odometer
/vehicles/{vehicleId}/odometer - GETGet Vehicle Information
/vehicles/{vehicleId}/information - GETGet Vehicle Smart Charging Policy
/vehicles/{vehicleId}/smart-charging-policy
How automating Enode works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- 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.
- See it proven. The program runs and shows you the result before it is allowed near your live Enode account.
- Grant access, then go live. You approve the specific Enode operations it may use — and only those.
Automate Enode with these
- HERE Tracking205 operations
- Traccar61 operations
- eDRV57 operations
- uebermaps endpoints56 operations
- Google My Business50 operations
- Weatherbit Interactive Swagger UI Documentation47 operations
- Waterlinked The Water Linked Underwater GPS38 operations
- OpenAQ36 operations
- Neutrinoapi Neutrino27 operations
- Staging Ecotaco .ecota.co27 operations
- Viator Documentation & Specification Merchant Partners27 operations
- Mashape GeoDB Cities26 operations
Categories
Questions about Enode automation
- Can HumDay connect to Enode?
- Yes. HumDay reads Enode's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 28 operations are documented.
- Do I need to write code to automate Enode?
- 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 Enode account.
- What can HumDay do in Enode?
- 13 of the 28 documented operations change something in Enode, and 15 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Enode 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 Enode is held behind that approval.
Where this came from
The operations above are read from a published API description for Enode at docs.enode.io/OpenAPI-Enode-v1.3.10.json. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.