Skip to content
hbeeken edited this page Oct 7, 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.


FourSquare/Swarm

Issues
  • Input events require https callback. There is a URL which can be polled (although this isn't the recommended usage, it is ok for the first pass of the node).
  • 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. This has been fixed along the same lines as some of the other more recent nodes.
  • API currently only supports polling check-in information of the authenticated user (https://developer.foursquare.com/docs/users/checkins - "self" is only supported). However, can get the list of friends for the authenticated user and then see which check-ins they've made so there may be a way around it. This needs clarification and looking into.
Inputs
  • New checkin for the authenticated user
  • New checkin for another user
  • New checkin from authenticated user's friends

Notes:

  • Only return a new check-in since the node was initialized
  • Polls every 15 mins
  • Could consider adding additional filter options - tag, category, geographic region...
Query
  • Poll the check-in URI to get the list of check-ins for the authenticated user ('self')
  • Poll the check-in URI to get the list of check-ins for a 'friend'

Notes:

  • Always return the most recent check-in since the node was initialized.
Outputs
  • Create a checkin event
Notes
  • Foursqure 8.0 split into Foursquare and Swarm. Foursquare being the "give me all the chinese restaurants near me" type capability and Swarm being the "check-in", more social capability (https://developer.foursquare.com/docs/2014update). Therefore anything check-in related needs to be named Swarm, as we have done.

Dropbox

Inputs
  • New file in a watched folder
Query
  • Get file contents
Outputs
  • Write to a file (replace/append)

Facebook

Inputs
  • Need to review API to see what events we can monitor
Query
  • ... lots ...
Outputs
  • Status update
  • Link share
  • Upload photo to a specified album

Delicious

https://github.com/node-red/node-red-web-nodes/tree/master/delicious

Inputs
  • ...
Outputs
  • Add a bookmark

Flickr

https://github.com/node-red/node-red-web-nodes/tree/master/flickr

Inputs
  • Added a photo (filter by tag etc)
Outputs
  • Upload photo

Instagram

Input events require https callback.

Inputs
  • Added a photo (filter by tag etc, photo OR video?)
  • Like a photo
  • A specific user has added a photo
Outputs

API is currently read-only... no outputs possible


Box

Inputs
  • ...
Query
  • Get file content
Outputs
  • Write to a file (replace/append)

Clone this wiki locally