I'm seeing these error responses on other endpoints, now.
Here's the result of an OAuth authenticated request for friends_ids:
{errors:[{code:53,message:Basic authentication is not supported}]}
Then verify_credentials Authenticating as the same user:
what endpoints are you still seeing this error format under? the change
should have been reverted in the case that you were mentioning.
TTYtter /set superverbose 1
TTYtter /whois [xxx]
[...]
url = https://api.twitter.com/1/users/show.json?screen_name=[xxx];
what endpoints are you still seeing this error format under? the change
should have been reverted in the case that you were mentioning.
On Sun, Aug 29, 2010 at 9:00 AM, Marc Mims marc.m...@gmail.com wrote:
* Raffi Krikorian ra...@twitter.com [100827 06:03]:
hi all.
this is most certainly
* Raffi Krikorian ra...@twitter.com [100830 05:48]:
what endpoints are you still seeing this error format under? the change
should have been reverted in the case that you were mentioning.
Like Cameron, I'm seeing it on users/show. Here's an example:
GET
* Raffi Krikorian ra...@twitter.com [100827 06:03]:
hi all.
this is most certainly a mistake on our part - we'll be reverting this
change.
Raffi, we're still seeing these unexpected error structures. When will
the change be reverted?
-Marc
On Fri, Aug 27, 2010 at 4:45 AM,
It looks like error responses have changed, at least for users/show.
I used to get:
{error:User has been suspended}
Now, I get:
{errors:[{code:63,message:User has been suspended}]}
I'm seeing that too. When did this change?
--
personal:
hi all.
this is most certainly a mistake on our part - we'll be reverting this
change.
On Fri, Aug 27, 2010 at 4:45 AM, Cameron Kaiser spec...@floodgap.comwrote:
It looks like error responses have changed, at least for users/show.
I used to get:
{error:User has been suspended}
Now,
* Raffi Krikorian ra...@twitter.com [100827 06:03]:
this is most certainly a mistake on our part - we'll be reverting this
change.
The new error format looks useful, especially if the error code allows
us to deal with multi-lingual error messages consistently. Obviously,
some advanced notice
All newer API methods have been returning API error codes for a while
now. We have been extremely sensitive to not breaking older behavior
(for backwards compatbility reasons), so older methods still return
the old format. We have been toying with the ability to get error
codes on all methods if
* Raffi Krikorian ra...@twitter.com [100827 06:54]:
All newer API methods have been returning API error codes for a while
now. We have been extremely sensitive to not breaking older behavior
(for backwards compatbility reasons), so older methods still return
the old format. We have been
10 matches
Mail list logo
