Automate dweet.io

What dweet.io is

Dweet.io allows users to share data from mobile, tablets, and pcs, and them to other devices and accounts across social media platforms. Dweet.io provides an API to access the different functionality of the Dweet.io service. Users can make REST calls to read and create dweets, lock and unlock things, and perform other calls. The API returns JSON and JSONP.

API host: dweet.io

What HumDay can do in dweet.io

2 documented operations change something in dweet.io.

• POSTCreate a dweet for a thing./dweet/for/{thing}
• POSTCreate a dweet for a thing./dweet/quietly/for/{thing}

What HumDay can read from dweet.io

These are the operations a schedule or a trigger can watch.

• GETReserve and lock a thing./lock/{thing}
• GETUnlock a thing./unlock/{thing}
• GETRemove a lock from thing./remove/lock/{lock}
• GETGet the alert attached to a thing./get/alert/for/{thing}
• GETRead the last 5 cached dweets for a thing./get/dweets/for/{thing}
• GETRemove an alert for a thing./remove/alert/for/{thing}
• GETCreate an alert for a thing./alert/{who}/when/{thing}/{condition}
• GETRead the latest dweet for a thing./get/latest/dweet/for/{thing}
• GETRead all the saved alerts for a thing from long term storage./get/stored/alerts/for/{thing}
• GETRead all the saved dweets for a thing from long term storage./get/stored/dweets/for/{thing}
• GETListen for dweets from a thing./listen/for/dweets/from/{thing}

How automating dweet.io works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live dweet.io account.
4. Grant access, then go live. You approve the specific dweet.io operations it may use — and only those.

Automate dweet.io with these

• Gambitcomm MIMIC356 operations
• Meraki Dashboard263 operations
• ClearBlade220 operations
• Influxdata Influx OSS197 operations
• Intellifi Brain77 operations
• Adafruit IO71 operations
• Ijenko IoE² IoT to create end user applications67 operations
• smart me64 operations
• Opto22 PAC Control55 operations
• KeyServ24 operations
• Hardware Sentry TrueSight Presentation Server23 operations
• Netatmo19 operations

Categories

• Iot

Questions about dweet.io automation

Can HumDay connect to dweet.io?

Yes. HumDay reads dweet.io's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 13 operations are documented.

Do I need to write code to automate dweet.io?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your dweet.io account.

What can HumDay do in dweet.io?

2 of the 13 documented operations change something in dweet.io, and 11 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my dweet.io account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to dweet.io is held behind that approval.

Where this came from

The operations above are read from a published API description for dweet.io at dweet.io/play/definition. Descriptions are the provider’s own words, not ours. Last published 2019-02-25.