Change in response codes for statuses longer than 140 characters and duplicate statuses
8 views
Skip to first unread message
Mark McBride
unread,
Mar 18, 2010, 2:31:52 PM3/18/10
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to twitter-ap...@googlegroups.com
Per popular request, we recently changed the api to return an error code of 403 when users attempted to post a status with over 140 characters. This currently works, except in the case that a long status can be reduced to under 140 characters by shortening URLs. In this case we return a 403 but successfully create the status.
As part of the same fix, we will also be returning 403s when a duplicate status is posted. This addresses another long standing request, where attempting to create a duplicate would return a 200 but fail to update. This fix will only apply to the api.twitter.com endpoints. You will not get a 403 posting a duplicate status using twitter.com endpoints.
This should only break applications that depend on 200 responses in the case of long statuses and duplicate posts.