Read the docs...thought the call was authenticated, but discovered
that the library I was using had a bug for situations where the call
included certain characters. The authentication failed, but the query
continued as an unauthenticated call. No error message. Bitch of a
time figuring out what
Hey Mike,
Sorry to hear you were having problems there. If the credentials were being
rejected we would have returned an X-Warning header in the response letting
you know.
There is more information about this in our rate limiting documentation:
https://dev.twitter.com/docs/rate-limiting#rest
