400: The request was invalid - but only for Verify requests and only recently

[bsteinback]

Hi there,
We’ve had a Twitter application running for over a year with no problems (thanks!), but have had a weird one just starting (around) yesterday. All our Verify requests are coming back with this error:

400:The request was invalid. An accompanying error message will explain why. This is the status code will be returned during rate limiting.
Relevant discussions can be on the Internet at:
http://www.google.co.jp/search?q=764db2f2 or
http://www.google.co.jp/search?q=027c96ee

Weirdly, all other requests appear to work fine.
Luckily (at least on our newest version) we have code to catch the ‘real’ verify error and throw out others, but it’s still very concerning (and fatal to the older version of our app). Any ideas?

By the way, two other notes:

1. The grammar on this (and other errors I’ve seen) is terrible. If someone could go thru and clean up the error messages, it would be greatly appreciated.
2. The relevant discussions weren’t relevant, and were mostly in Japanese

[episod]

This is likely related to what I’m investigating here: [node:12782].

The error message you’re mentioning comes from the library you’re using, not the Twitter API. It’s best when you’re running into an error to try to get to the raw response of the API.

[bsteinback]

Thanks Taylor. I suspected the error I was seeing might come from my API (Twitter4j). I had hoped they would be kind enough to pass Twitter’s errors thru unmodified, but alas I guess not.

I’ll try to dig thru Twitter4J to get the exact calls I’m making. I’ll post it here if I get it.

[bsteinback]

I’m also following the other thread, so if you crack it I’ll hopefully see the result there (I guess I should post there also to keep the info in one place).

[farreachsocial]

@bsteinback did you solve the problem?