You can get updates as an Atom feed. If you want to contribute or discuss the future or current state of the API, feel free submit a pull request or open up a GitHub issue in our open Flowdock API documentation GitHub repository.
User ids in messages
January 14, 2014
All user ids in messages in all endpoints are now formatted as strings, as documented. A bug caused message user ids to be formatted as integers when messages were fetched via REST API.
October 24, 2013
message_id is the id of the message being commented. In push api it’s also possible to specify the
message_id to post a comment to a particular message. See further details from the respective documentation page.
Contrary to the comment messages received from the streaming api or REST message endpoints, the
content is just a plain string and the event cannot be specified at this point to have a stable api for forwards compatibility.
Organization data format
October 4, 2013
In order to provide more information and a link to organization resource, the
organization attribute of flow will change from the human readable name of organization (string) to organization information (object).
In addition, the attribute
id of organization will now be a persistent numeric identifier, instead of the current subdomain that can be changed by the users. The flow and organization resource documentation has been updated accordingly.
Flow ID format
April 11, 2013
To enable more flexible changing of flow URLs and email addresses, flow IDs will be separated from these. This means that IDs can’t be used to construct API endpoint URLs. Instead,
url field should be used.
Starting from May 27 2013, the flow IDs will be UUIDs with no connection to URL format.
Currently messages use ID format separated by colons whereas in flow data, organization and flow name is separated by slash. After UUID format is deployed, we will also change flow IDs to use colons.