Klout Developer Blog

KloutPass: Discover And Recognize Your Influencers

The Klout API is used in a variety of innovative ways. We have integrations with Social CRM systems, Social Analytics and Social Media Managers, as well as a healthy dose of consumer applications. The running thread throughout the majority of the applications running on the Klout Platform is the desire to discover and identify influential individuals across social media platforms. Today, we are introducing KloutPass, a system that allows developers to authenticate and register their users with Klout, enabling them to identify their influence across platforms, and to recognize and reward them. KloutPass releases with a JavaScript SDK enabling a simple integration with a minimum of dev time.


We are building a set of SDKs and libraries for popular platforms and languages (JS, iOS, etc.) to ensure that a KloutPass integration is simple and intuitive for developers of all skill levels. However, as with any oAuth implementation, it's crucial that you understand its specifications, limitations and strengths. We built KloutPass using the OAuth 2.0 v2-25 Draft as a guide. Klout has chosen the implicit and authcode grant patterns for this implementation.

With KloutPass, you will receive a kloutId (their score and an authentication token) for any user that successfully logs in or registers with Klout. Klout allows login with either Sign-in With Twitter or FacebookConnect. Therefore, you can now easily obtain a kloutId for a user, regardless of which network your application has identified them by. This, of course, requires the user to authorize and approve your application. At this time we are not offering any heightened permissions with a token—there are no enhanced scopes. Imagine the features that we can make available in the future with this simple building block. With the V2 Klout API, you can lookup that user by kloutId and get their Klout Score, topics they are influential about, and influence graph.

Users can manage the applications they have authorized in their Klout Settings. Some users may have found this easter egg lying dormant on the new Klout.com design.

For more information about implementing KloutPass, take a look at the sweet documentation. The OAuth API requires separate keys from your V1 or V2 API keys, and we are moderating the approval of keys for KloutPass at this time. Please provide accurate and complete information about your application when generating a key. You can do this on the Mashery Portal. We have also updated our Platform Terms of Service to accommodate these changes.

Thanks go to the KloutPass lead engineer, Jieren Chen.

Feel free to tweet to @harmophone, @KloutPass, or @KloutAPI with any questions.


Privacy is central to what Klout does and enters into every decision and product. KloutPass is no different. We do not provide access to a user's email address or any other personally identifying information through oAuth. The client-side Javascript SDK utilizes some of these elements to signal to the user that the authorization was successful. By using KloutPass, as a developer, you absolutely must adhere to our terms of service, privacy policy, and the terms of any of our data providers.

V1 API Sunset

It always bears repeating: the version 1 API will be retired on December 31st, 2012. All developers are advised to move to the V2 API as soon as possible to minimize disruption. The V2 API is awesome. You should use it. Not only is it on an order of magnitude more performant, we continue to add features to it.