It's easy to work with Clever's REST API and authentication routines without needing specialized libraries. If you can issue & receive HTTP requests and process JSON response bodies, you have everything you need for a Clever integration.
You don't really need a client library for OAuth 2.0 – the flows boil down to simple HTTP. If you have a HTTP interface in your programming language of choice, you already have an OAuth 2.0 client.
OAuth 2.0 also isn't just "one thing" — it's a collection of approaches for service providers (like Clever) and client applications (like yours) to authorize users and authenticate requests.
Often OAuth 2.0 libraries serve both audiences simultaneously, leaving you with a heavy duty library better suited for service providers when you just want to do some basic HTTP.
When evaluating OAuth 2.0 libraries, make sure you're not working with an OAuth 1.0A library -- Clever does not support the more complicated OAuth 1.0A authentication.
Our sample code demonstrates how to use common HTTP libraries with Clever's OAuth 2.0 implementation.
- omniauth-clever - an OmniAuth strategy for Ruby-based applications
If you prefer to work with objects more native to your favorite programming language, Clever offers a few libraries that wrap REST API access with object interfaces. While these libraries won't necessarily help you obtain access tokens, they do make it easier for you to retrieve and operate on Clever data once you've obtained them.
These libraries are community supported - they are not actively maintained by Clever, although we do review & merge incoming pull requests.