Libraries and Sample Code

Use this page to find community-supported Clever libraries, understand when you do not need a library, and review sample code.

❗️
The Clever iOS SDK has been deprecated
If you are building Clever SSO for a native iOS application, see the updated iOS documentation here: https://dev.clever.com/docs/ios.

🚧
Community-supported libraries are not maintained by Clever
Clever does not actively maintain these libraries, though Clever may review and merge incoming pull requests.

You may not need a library

Clever’s REST API and authentication flows work over standard HTTP.

If your stack can:

send HTTP requests
receive HTTP responses
parse JSON

then you already have everything you need to build a Clever integration.

OAuth 2.0 libraries

You usually do not need a specialized OAuth client library for Clever. In most cases, the OAuth flow only requires standard HTTP requests.

Many OAuth libraries try to support both service providers and client applications, which can make them heavier than necessary if your goal is simply to authenticate users and exchange tokens.

🚧
Versions matter
Make sure you are evaluating OAuth 2.0 libraries, not OAuth 1.0a libraries. Clever does not support OAuth 1.0a.

Clever API libraries

Clever does not maintain official API libraries.

If you want to generate your own client library, the Swagger file is available here:

https://github.com/Clever/swagger-api

Clever also offers several community-supported libraries that wrap REST API access with object interfaces. These libraries generally help with data access after you already have tokens.

Community-supported libraries

Sample code

This demo application includes Secure Sync, SSO, and Events sync examples:

https://github.com/KatieTGardner/clever-demo-app