Right now, our twitter api is out of synch with the official Twitter api - we are working right now to update it.
On Fri, Jun 11, 2010 at 12:19 PM, Richard Hirsch <[email protected]>wrote: > to use it you have to do something like this: > > curl --dump-header headers -d "token=31FGZ0R0M15NTD2LSOS0BKC5Y0P5JOVAC" > http://api2.esme.apigee.com/api2/session > > Don't worry - token is a fake one. > > D. > > On Fri, Jun 11, 2010 at 10:42 AM, Richard Hirsch <[email protected]>wrote: > >> APIGee allows you to monitor and test api usage. I've signed up and the >> api2 api is available with api2.esme.apigee.co. >> >> I'll do the twitter api next. The advantage with using apigee for this api >> is that we can see exactly how various twitter clients are using ESME and >> what sort of problems they are having. I'll keep you abreast on what I >> learn. This api is available with this URL: twitter.esme.apigee.com. >> Please use this when connecting with any client (Tweetdeck, etc.) >> >> Have fun. >> >> D. >> >> >
