Hi Matt, Had a close look at this. My bad. I have always been doing a POST for replies not GET as documented. I guess you tightened up on this recently. Thanks.
Rhys On Apr 23, 5:09 pm, Matt Sanford <[email protected]> wrote: > Hi Rhys, > > Bas request is generally something like unescaped characters in > the URL. Can you try with curl and send the URL causing the problem? > > Thanks; > – Matt Sanford / @mzsanford > Twitter API Developer > > On Apr 23, 2009, at 09:08 AM, rhysmeister wrote: > > > > > Hi Matt, > > > I'm getting > > > "Error: The remote server returned an error: (400) Bad Request." > > > Definatly not rate limiting here. > > > Rhys > > > On Apr 23, 4:59 pm, Matt Sanford <[email protected]> wrote: > >> Hi Rhys, > > >> Both should work at the moment. We still have both configured > >> and > >> I just did some curl requests with my test account and verified it. > >> Are you getting any specific error? curl requests with headers > >> (curl - > >> v, but be sure to obscure the Authorization header) always help in > >> times like these. > > >> Thanks; > >> – Matt Sanford / @mzsanford > >> Twitter API Developer > > >> On Apr 23, 2009, at 08:51 AM, rhysmeister wrote: > > >>> I've just noticed some @reply functionality is not working in my app > > >>> I was aware of the change to "mentions" but not that this involved a > >>> change in url tohttp://twitter.com/statuses/mentions.formatisthe > >>> oldhttp://twitter.com/statuses/replies.formatdead?Any chance of > >>> reinstating if so? > > >>>http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses- > >>> mentions > > >>> Rhys
