Hi All,
I have just started to put together a small Twitter application but
every so often I am seeing either a 401 Unauthorized or 502 Bad
Gateway when acquiring a request token. Would it be normal to see this
during twitter 'over capacity' periods?
Cheers
James
Is there anywhere in the documentation that shows what fields you
could expect in the json responses for the api methods or is it just a
case of hit the service and work out what fields there are to play
with from the responses?
I would imagine this one as it is on dev which is more up to date and
seems more in keeping with their other REST formats.
http://api.twitter.com/version/favorites/:id/create.format
On May 21, 6:21 am, Jebu Ittiachen wrote:
> As per apiwiki.twitter.com create favorite is
>
> http://api.twitter.c
Tried changing the the callback url to oriflamenews.com? Looks like it
is complaining because you have set the subdomain to www on the
callback but your pages automatically redirect to a domain url without
it. Least thats my best guess.
On May 25, 7:28 am, Teofilus wrote:
> Sir, I HAVE a problem,
Only info I have found so far is
http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors
On May 28, 1:02 am, Michael Cameron wrote:
> So i am writing my catch expressions for twitter when parsing the
> response from twitter is there any error codes or definite strings for
> certain reasons. ex
