OAuthpocalypse? Have No Fear, ApiGeeks! »

The Twitter API is one of the most popular APIs on our platform and with Twitter shutting off basic auth and moving to OAuth tomorrow, we wanted to reassure you that Apigee is ready for the OAuthpocalypse with full support for APIs which use OAuth.

Here's how to do it, using the Twitter API as an example:

1. Do the OAuth dance with the canonical API endpoint (e.g. api.twitter.com).

2. Once you have a user's token, use it to sign requests' base strings, which you would also build using the canonical endpoint from step 1.

3. Then send those signed requests to your Apigee URL, such as twitter.myusername.apigee.com.

In this way traffic can flow to and from Twitter via your Apigee API using OAuth.

Let us know if you run into any questions or issues- visit our support site or ping us on Twitter at www.twitter.com/apigee. Good luck with the big switch!