Test Firehose Webhook in Enode
A documented Enode operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Test Firehose Webhook
- POSTChanges data · Webhooks 🧪
api.test.enode.io/webhooks/firehose/test
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. Because this one changes data, it cannot run until you have explicitly granted it.
Other Enode operations
- Create Charging LocationPOST · changes data
- Deauthorize UserDELETE · changes data
- Update Firehose WebhookPUT · changes data
- Delete Charging LocationDELETE · changes data
- Update Charging LocationPUT · changes data
- Disconnect VendorDELETE · changes data
- Start Watching VehiclePOST · changes data
- Control ChargingPOST · changes data
Questions
- Can HumDay test firehose webhook 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.
- Will this change my Enode data?
- Yes — this is a POST operation, so it changes something in Enode. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- 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.