Home/ Questions/Q 8560907
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T16:23:02+00:00

I have problems with the new Twitter API: v1.0 is working without problems, but

  • 0

I have problems with the new Twitter API: v1.0 is working without problems, but if I change the URL to v1.1 I get all the time a error “400 Bad request” (seen with Firebug).

Example:

https://api.twitter.com/1/statuses/user_timeline.json?screen_name=twitterapi

This is working like a charm, everything works as excepted.
Simply changing the URL to .../1.1/... and I get a Bad request error and even to JSON error response or even some content at all.

https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=twitterapi

Note: It couldn’t be a rate limitation, because I accessed the URL the first time ever.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=twitterapi redirects me to https://api.twitter.com/1/statuses/user_timeline.json?screen_name=twitterapi

    Looks like 1.1 is the same thing as 1

    UPD: Looks like this is a rate limit (as 1.1 link worked for me 2 hours ago). Even if you hit API page for the first time, some of your apps (descktop or mobile) could use API methods.

    UPD2: in 1.1 400 Bad request means you are not autorized (https://dev.twitter.com/docs/error-codes-responses, https://dev.twitter.com/docs/auth/oauth#user-context). So you need to get user context

    • 0