API reference
The public AnyOAuth authentication contract, generated from the same schema as the SDKs.
On this page
Base URL: https://api.anyoauth.com. Contract version: 0.2.0.
Endpoints
POST /v1/login/sessionClean callback loginRecommended clean-callback flow. Register a fresh 32-byte base64url session key from your backend and retain it in a browser-bound server session. Navigate the browser to authorization_url. The key and client secret must never appear in URLs. AnyOAuth returns to the exact registered callback without query parameters or fragments on success and failure. No automatic retries.
POST /v1/login/resultLogin resultFetch the clean-callback result from your backend using the original session key, client credentials and callback. Pending reads do not consume the session. A succeeded result carries profile; a failed result carries error. Terminal results are consumed atomically once; expiry, replay and invalid sessions return 400. Verify the initiating browser cookie before calling. No automatic retries after ambiguous failure.
GET /authorizeLegacy browser authorizationConstruct this URL locally and navigate the browser. Persist state/verifier in the initiating application session; validate and consume the transaction on callback. Never include a client secret.
POST /v1/tokenCode exchangeClient credentials are in the JSON body, not Basic auth. One-time redemption; no automatic retries after ambiguous failure. Token expires in 900 seconds.
GET /v1/profileProfileNormalized identity; null fields are legitimate. Use subject, not email, as account key.
POST /v1/revokeRevocationNo body. Syntactically valid bearer tokens are revoked idempotently. Does not terminate the customer app session.
GET /api/providersProvider availabilityDeployment-wide status, not project-specific authorization. Browser clients use their backend for this API.
Machine-readable contract
OpenAPI 3.1.1 describes HTTP operations. JSON Schema 2020-12 describes their payloads. These are generated from the canonical public integration contract, not independently maintained reference tables.
Integration model
Start with the managed SDK: mount auth.router(), then call browser startLogin('google'), getProfile() and logout(). The backend validates the clean callback and manages an authenticated session. The HTTP session/result endpoints remain available for custom integrations; the legacy code/profile-token endpoints remain compatible.
Quickstart · React, Vue, Astro and other frontends · Custom sessions and routes. AnyOAuth does not return upstream provider tokens or implement browser-only OAuth.