Get Vehicle Odometer in Enode
A documented Enode operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get Vehicle Odometer
- GETReads data · Vehicles
api.test.enode.io/vehicles/{vehicleId}/odometer
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Enode operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Enode operations
- Create Charging LocationPOST · changes data
- Deauthorize UserDELETE · changes data
- Update Firehose WebhookPUT · changes data
- Test Firehose WebhookPOST · changes data
- Delete Charging LocationDELETE · changes data
- Update Charging LocationPUT · changes data
- Disconnect VendorDELETE · changes data
- Start Watching VehiclePOST · changes data
Questions
- Can HumDay get vehicle odometer in Enode?
- Yes. This operation is published in Enode's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Enode account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Enode.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Enode account.
Where this came from
Read from a published API description for Enode at docs.enode.io/OpenAPI-Enode-v1.3.10.json. The description above is the provider’s own wording, not ours. Last published 2021-06-21.