Today we’re releasing a major upgrade to our platform that will significantly impact parts of our API. These changes are necessary to allow our platform to scale at the tremendous rate we’re seeing and provide vastly improved reliability.
/stories/tweets
The /stories/tweets API call now includes a “uuid” (a 32 char hex string) for each Tweet returned. This UUID represents the Tweets position within the timeline for that story. The from_id parameter, which used to accept the Tweet ID of the previous Tweet to page from now accepts the UUID of the previous Tweet to page from. If you pass the Tweet ID instead, you will get an error.
This is the most disruptive change and only affects clients that page tweets. Your underlying paging logic can remain the same, but you will need to pass our API a different value for the from_id.
/stories/recent & /stories/popular
Both the /stories/recent and /stories/popular API calls will no longer accept a domain parameter. This is due to a performance issue that we have identified and we hope to restore this functionality in the coming months.
The Stories API docs have been updated with these changes, please refer to them for more details and examples.
Any reason why the “retweet” field would be missing from results from the stories API? It disappeared
Check this and you’ll see that it’s no longer present: http://api.tweetmeme.com/stories/popular.json
You specify the field’s availability in the Stories API docs and describe it as such: “retweet: string a tweet to send in order to retweet this story”
Dan,
To continue scaling the platform we stopped ‘pre-making’ short urls for every link and in doing so it made it impossible to also pre-create tweets, we will soon be publishing details of a new method that will generate you a 140 character tweet based upon a url, which you can call when you need it, this is much more scalable + is better for developers as you can customize each retweet.