We have released a bunch of improvements to the Flowdock API during the past couple of months: OAuth 2.0 support, commenting and better message responses. These changes should make it even easier for you to extend Flowdock in a way that makes it more useful for you and your team.
OAuth 2.0 support
Flowdock now supports OAuth 2.0 as an authentication mechanism. With OAuth 2.0, you no longer need to provide a user’s email address and password when using the REST API. Users simply authorize your app or service to use Flowdock on their behalf.
This is great for both users and developers: users get a centralized location where they can control what type of access their applications have (or revoke them if necessary), and API developers no longer need to deal with the hassle and security implications of storing a user’s email address and password. Because of this, OAuth 2.0 is now the recommended authentication mechanism.
Adding OAuth 2.0 support is easy to do using a ready-made OAuth 2.0 library. To help you on your way, we released the Ruby OmniAuth Flowdock strategy.
OAuth 2.0 and our improved CORS support (better error handling, access_token query authentication) give you a fairly broad range of possibilities for making Flowdock-powered web-based apps and integrations.
Comments to message threads
The API is no longer limited to posting new chat or team inbox messages. You can now send comments to existing content, which will be added to that item’s conversation thread.
-d external_user_name="mikey" -d event="comment" -d message_id="5" \
You can also upload files as a comment by posting an event of type
file to the same sub-resource URL or by specifying a message_id.
Better responses when sending messages
Previously, when sending messages using the REST API, the server responded with a success or error status message. The messages resource has been changed to respond with a JSON representation of the message, including all metadata. The HTTP response also includes a Link field with a URL resource to which further comments can be posted.
These changes should make it easier to create conversations around a single item using the API.
So, what can I do with this?
Here are some examples of what can be done using the API:
- Send an inbox item when your build or deploy starts, and comment it with a status message when it completes.
- Synchronize an issue’s comments between Flowdock and your issue tracker.
- Your own Flowdock client.
And, of course, countless other applications that we can’t even imagine.
As always, feedback is very much appreciated! If you’ve got questions or comments, you can send them to me or firstname.lastname@example.org.