REST API REST API v1.1

Error in Getting User Info -- 1/users/show.json?include_entities=true&user_id=******** (1)

For which reason you make such API limitation? Troubles with friends/ids and users/lookup (1)

GET statuses/retweets/:id (4)

retweet_count and mention_count at user object level (1)

Followers/ids inconsistencies (1)

When will search 1.1 break a while True loop? (1)

Styling embedded timelines (1)

Max length char (1)

How can I check if a user has already authorized the app? (2)

Delete please. Double post (1)

Best way to get recent tweets from a contact (1)

Entities not returning url structure, when the url has special characters (2)

Getting error 400 while hitting twitter API since 16 Nov 2012 (2)

Users/lookup and 502 HTTP Errors count against rate limit (5)

Getting 'random' 401 errors since 13 Nov for update v1 API calls (2)

API endpoint to upload banner image (8)

Solution design: Retrieving conversations (1)

Get only geolocalized tweets (2)

Since 14th nov the friends and followers endpoints are returning incorrect headers (2)

Use of brackets in search queries (2)

The "retweeted" and "favorited" nodes of the tweet object and "following" node of the embedded user object do not work as expected (1)

Twitter GET Search returns empty result (2)

home_timeline.json return error 404 (page not found) if used through secure connection (https)? (4)

Upgrade from v1 to v1.1 "could not authenticate you" status/update (3)

Getting latest tweet(s) from Friends without hitting Call Limit (1)

Twitter GET statuses/user_timeline problem (2)

Will a multi protocol client with separated Twitter and none-Twitter be 1.1 compliant? (2)

A Twitter account has gone offline (Poker_Flat in this case) around 01:00 AM UTC time 09/11/2012 (dd/mm/yyyy) and this breaks the /users/lookup API request with a 500 (internal error 131) problem (1)

Does new API version require any changes to user authorization code? (3)

While fetching data from API it uses more RAM memory and system gets hanged (1)

Powered by Discourse, best viewed with JavaScript enabled