Create a dweet for a thing in dweet.io
A documented dweet.io 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
Create a dweet for a thing.
- POSTChanges data · dweets
dweet.io/dweet/quietly/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. Because this one changes data, it cannot run until you have explicitly granted it.
Other dweet.io operations
- 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
- Get the alert attached to a 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 create a dweet for 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.
- Will this change my dweet.io data?
- Yes — this is a POST operation, so it changes something in dweet.io. 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 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.