Get a specific transaction in eDRV
A documented eDRV 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 a specific transaction
- GETReads data · Transactions
/v1/transactions/{id}
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 eDRV 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 eDRV operations
- Create a new charge stationPOST · changes data
- Create a new tokenPOST · changes data
- Create a new driverPOST · changes data
- Create a new locationPOST · changes data
- Create a new connectorPOST · changes data
- Create connector with parametersPOST · changes data
- Delete a smart charging scheduleDELETE · changes data
- Use to delete a charge stationDELETE · changes data
Questions
- Can HumDay get a specific transaction in eDRV?
- Yes. This operation is published in eDRV'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 eDRV account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in eDRV.
- 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 eDRV account.
Where this came from
Read from a published API description for eDRV at developers.edrv.io/openapi/5f15c43c87b0d6001ea97414. The description above is the provider’s own wording, not ours. Last published 2020-12-30.