forked from node-red/node-red
-
Notifications
You must be signed in to change notification settings - Fork 0
Web Nodes outline
Nick O'Leary edited this page Aug 29, 2014
·
10 revisions
This is a list of web APIs we want to start creating nodes for.
For each service there are some thoughts of the types of input/query/output capabilities we might want. Some need further investigation to see what they expose in their API.
Some use HTTP(S) callback for event notification. This will only be possible with a public facing host e.g. bluemix. Some have alternative polling based apis which we can use.
- Input events require https callback.
- Their OAuth authentication implementation requires a predefined callback uri which cannot be overridden by the application. This makes it impossible to create an authentication flow as we've done for twitter/flickr.
- New checkin for the authenticated user
- New checkin for another user
- New checkin from authenticated user's friends
Could consider adding additional filter options - tag, category, geographic region...
- Create a checkin event
- New file in a watched folder
- Get file contents
- Write to a file (replace/append)
- Need to review API to see what events we can monitor
- ... lots ...
- Status update
- Link share
- Upload photo to a specified album
- ...
- Add a bookmark
https://github.com/node-red/node-red-web-nodes/tree/master/flickr
- Added a photo (filter by tag etc)
- Upload photo
Input events require https callback.
- Added a photo (filter by tag etc, photo OR video?)
- Like a photo
- A specific user has added a photo
API is currently read-only... no outputs possible
- ...
- Get file content
- Write to a file (replace/append)