This page is for AUTH V1, which is being retired around April 2027. If you are starting something new, or migrating, the equivalent is Client libraries (AUTH V2) — V2 is standards-compliant, so the library configuration is shorter and discovery actually works there.
POST /oauth/token accepts both application/x-www-form-urlencoded (the RFC 6749 §3.2 default) and application/json, and reads client credentials from either the request body or an Authorization: Basic header (RFC 6749 §2.3.1).
Quick library status
Each library below completes the whole flow — browser consent, authorization code, token — and theaccess_token it returns works on every authenticated endpoint.
Every library here needs the same thing: the two endpoint URLs and your credentials. Nothing on this page requires discovery, and for V1 you should not use it — see the warning above.
The libraries worth a second look are the three that prefer to discover:
openid-client v6, oauth4webapi and Spring Security. Left to their defaults they will fetch a metadata document and configure themselves from it, which for a V1 app is exactly the wrong outcome. Their snippets below set the endpoints inline instead, which is a one-line difference and removes a network call from your startup path. If one of them misbehaves, compare its requests with the raw HTTP reference — that is the exact wire format the server expects.
The wire format
client_secret for code_verifier.
Python authlib
Python requests-oauthlib
Python httpx-oauth
Node openid-client v6
Node oauth4webapi
Node simple-oauth2
Node passport-oauth2
Node @badgateway/oauth2-client
Java Nimbus OAuth 2.0 SDK
Java Spring Security OAuth2 Client
authorization-uri and token-uri directly rather than issuer-uri, as above — this is the one place a V1 app must not take the shortcut. issuer-uri resolves, and it resolves to V2: Spring reads /.well-known/oauth-authorization-server, configures itself for /oauth2/*, and your V1 client_id is then rejected with invalid_client. Default client_secret_basic works either way.
Java Google OAuth Client for Java
Java scribejava-core
Go golang.org/x/oauth2
PHP league/oauth2-client
Raw HTTP
Other OAuth libraries (inferred from RFC compliance)
These libraries have no snippet on this page. Most wrap one of the libraries above; the rest follow the same RFC defaults Simkl accepts. The status below follows from that.
If you hit a library not on this list, the sanity check is one HTTP capture: confirm the token POST hits
https://api.simkl.com/oauth/token, sends client_id / code / redirect_uri / grant_type (and client_secret either in the body or in Authorization: Basic), and see what comes back. If the request looks RFC-shaped and you still hit an error, let us know — we’d appreciate the capture so we can promote the library to the live matrix.
See also
OAuth 2.0 walkthrough
Confidential (server-side) flow.
Public PKCE walkthrough
Mobile / SPA / desktop flow without
client_secret.PIN flow
TV / console / CLI flow with a 5-character code.