Get the alert attached to a thing in dweet.io
A documented dweet.io 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 the alert attached to a thing.
- GETReads data · alerts
dweet.io/get/alert/for/{thing}
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 dweet.io 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 dweet.io operations
- Create a dweet for a thingPOST · changes data
- Create a dweet for a thingPOST · changes data
- Reserve and lock a thingGET · reads data
- Unlock a thingGET · reads data
- Remove a lock from thingGET · reads data
- Read the last 5 cached dweets for a thingGET · reads data
- Remove an alert for a thingGET · reads data
- Create an alert for a thingGET · reads data
Questions
- Can HumDay get the alert attached to a thing in dweet.io?
- Yes. This operation is published in dweet.io'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 dweet.io account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in dweet.io.
- 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 dweet.io account.
Where this came from
Read from a published API description for dweet.io at dweet.io/play/definition. The description above is the provider’s own wording, not ours. Last published 2019-02-25.