You might try Apigee's test console for the Twitter API: http:/app.apigee.com/console/twitter If you do, let us know how it works for you. We're always interested in feedback on how to make it better! Thanks, Marsh On Sep 1, 10:36 pm, Andrea Stagi stagi.and...@gmail.com wrote: Hi, I'm
Not sure how much this would help you, but you can see any header that has been sent via Apigee's test console via the request tab. http://app.apigee.com/console/twitter If there's more information you'd like to see in there, do let us know, as we're always working to improve the test console.
I see it too. Here's a cached version of the response: http://app.apigee.com/console/apigee-console-snapshots-128331720_b7a1fe22-6ec8-4996-ba1a-2720227c896c/rendersnapshotview The same request with xml seems to be working fine:
We (I work at @apigee) are refreshing the WADL descriptionhttps://github.com/apigee/wadl-library/blob/master/twitter/api.twitter.com.xml that drives the API Console for Twitter in the next few days to make sure that it is as up-to-date as possible. And if anyone has feedback about what would
Whoops, I put percent-encoded on text of the web intent link where it wasn't necessary. Feedback tweeted @apigee http://twitter.com/intent/tweet?text=@apigee is the proper way to send it. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:
Here's a strange issue… When I use the Apigee API Console to make a request, it throws a 400 Bad Request error (examplehttps://apigee.com/console/apigee-console-snapshots-130422600_bc5252c1-2e88-49e1-a1ed-550494434a7b/rendersnapshotview), unless I define the User-Agent header