Reverse Auth: enabled by default

Friday, 2 November 2012

Shortly after we announced our iOS integration last year, we heard from developers that they needed a way to securely obtain access tokens for iOS users that could then be used server-side to perform long-running data processing or to integrate with existing business logic. So, we launched Reverse Auth –– a simple process that lets apps use the native iOS5+ integration to obtain user access tokens, which can then be used in combination with an application’s keys to make authenticated calls to the Twitter API. At the time, and until now, you had to contact us to obtain access to the endpoint required for Reverse Auth. This step led to additional time-to-market for many applications.

Starting today, Reverse Auth is now available by default for any new or existing application keys. So, you no longer have to contact us to get access to the endpoint. Applications that previously had access to the endpoint will continue to function as expected. To help with your integrations, this sample project demonstrates how to perform the Reverse Auth process on both iOS5 and iOS6. If you have questions or run into any problems with your integration, please post them in the Mobile Development discussion forums.