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
Hope that helps,
@themattharris <https://twitter.com/intent/follow?screen_name=themattharris>
Twitter, Inc.
On Wed, Aug 10, 2011 at 8:50 AM, mike3s <[email protected]> wrote:
> 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 was happening; had to reverse engineer the
> library and step through it.
>
>
> On Jul 4, 2:09 pm, "Mo'b Mo'b" <[email protected]> wrote:
> > Authenticated Rate Limit --- 350 Calls per hour.
> > Unauthenticated Rate Limit --- 150 Calls per hour.
> >
> > Please read the docs.
>
> --
> Have you visited the Developer Discussions feature on
> https://dev.twitter.com/discussions yet?
>
> Twitter developer links:
> Documentation and resources: https://dev.twitter.com/docs
> API updates via Twitter: https://twitter.com/twitterapi
>
> Unsubscribe or change your group membership settings:
> http://groups.google.com/group/twitter-development-talk/subscribe
>
--
Have you visited the Developer Discussions feature on
https://dev.twitter.com/discussions yet?
Twitter developer links:
Documentation and resources: https://dev.twitter.com/docs
API updates via Twitter: https://twitter.com/twitterapi
Unsubscribe or change your group membership settings:
http://groups.google.com/group/twitter-development-talk/subscribe
