The Twitter API issue tracking system is used to report and give you update on bugs found in our APIs and widgets. Before reporting any new issue, be sure to check developers discussions and the issues list. Also note that existing issues are automatically linked to the documentation pages and discussion threads they're related to.
- In progress
| ID | Summary | Status | Last update |
|---|---|---|---|
| #1226 | Tweets streamed in the Streaming API are missing the favorite_count field | In progress |
4 weeks 5 hours
ETA: Within a week |
| #917 | There is no method of API 1.1 to get a user's own list. | In progress |
25 weeks 5 days
ETA: Unknown |
| #823 | trends/place not updated in last few hours. | In progress |
32 weeks 6 days
ETA: Unknown |
| #428 | search error 131 with small ordinate (< 0.001) + some radius | In progress |
1 year 3 weeks
ETA: Unknown |
| #5 | REST API responds with HTML instead of JSON or XML for certain error conditions | In progress |
1 year 23 weeks
ETA: Within a month |
| #39 | Tweets produced by some iOS5 apps are mistakenly attributed to "iOS" instead of the app name | In progress |
1 year 23 weeks
ETA: Unknown |
| #141 | Geocode search volume lower than expected | In progress |
1 year 37 weeks
ETA: Unknown |
| #69 | Possible values are not documented | In progress |
1 year 45 weeks
ETA: Unknown |
| #17 | 502 errors when requesting data that takes too long to process | In progress |
1 year 48 weeks
ETA: Unknown |