SDKs and installation
Install verified registry packages and use examples that match their released API.
On this page
Current SDK source
The Quickstart uses the simple managed router and browser helpers from the
current SDK source. These helpers are not included in the published 0.1.0 packages.
From this repository checkout, install the Node and browser SDKs into your app:
# Run in your application, using the path to your AnyOAuth checkout:
npm install /path/to/anyoauth/sdks/node /path/to/anyoauth/sdks/clients/ts expressThe backend mounts auth.router(); the frontend calls anyoauth.startLogin('google'),
anyoauth.getProfile() and anyoauth.logout(). Frontend framework tabs
cover React, Vue, Astro, HTML, Svelte, Next.js and Nuxt.
Other backend languages use startLogin and completeLogin from their current SDK
source under sdks/; choose your language.
Install a published package
Ten SDK targets have verified 0.1.0 registry releases. Pin the version shown below:
| Target | Install / dependency | Registry |
|---|---|---|
| Node.js / TypeScript | npm install @anyoauth/node@0.1.0 | npm |
| Browser TypeScript | npm install @anyoauth/client@0.1.0 | npm |
| Expo | npm install @anyoauth/expo@0.1.0 | npm |
| Python | python -m pip install anyoauth-sdk==0.1.0 | PyPI |
| PHP | composer require anyoauth/anyoauth:0.1.0 | Packagist |
| Ruby | gem install anyoauth-sdk --version 0.1.0 | RubyGems |
| Rust | cargo add anyoauth-sdk@=0.1.0 | crates.io |
| Elixir | Add {:anyoauth_sdk, "0.1.0"} to mix.exs dependencies | Hex |
| Java | Maven coordinate com.anyoauth:anyoauth:0.1.0 | Maven Central |
| Kotlin | implementation("com.anyoauth:anyoauth-client:0.1.0") | Maven Central |
Java’s Maven dependency:
<dependency>
<groupId>com.anyoauth</groupId>
<artifactId>anyoauth</artifactId>
<version>0.1.0</version>
</dependency>Complete an integration
Start with the simple SDK quickstart. For an existing 0.1.0 installation,
use the published-package walkthrough. It uses
the real released Node exports and includes backend login/callback routes,
application sessions, frontend buttons, profile retrieval and logout.
For the Express example, also install express and express-session. Other backend
frameworks can use the same SDK with their own session storage. Project Integration
in the dashboard fills your client ID and exact registered callback into the example.
Released API versus newer source
Published 0.1.0 server SDKs expose authorization-code exchange, profile, revocation,
provider status and state/PKCE helpers. In Node, the names are createTransaction,
authorizationUrl, validateCallback, exchangeCode, profile, revoke and
providers. Follow the v0.1.0 README for other languages’ method casing.
The browser and mobile packages contain secret-free local helpers; a confidential backend redeems the code. Browser buttons that navigate to backend routes do not need a browser SDK or a client secret.
Managed createAuth adapters, startLogin/completeLogin, and named browser
startLogin, getProfile and logout exports are newer unreleased source APIs.
They are not in these registry packages. Current source and generated method
contracts may describe those upcoming APIs; use versioned release documentation
when installing 0.1.0. Never replace a published immutable version with new code.
Go and Swift
Go and Swift use versioned GitHub source distribution directly:
go get github.com/AnyOAuth/anyoauth-go@v0.1.0For Swift Package Manager:
.package(url: "https://github.com/AnyOAuth/anyoauth-swift.git", exact: "0.1.0")Pending registries
NuGet (AnyOAuth.SDK) and pub.dev (anyoauth_client) are not yet published.
Use their versioned source repositories and native build instructions;
do not use a NuGet or pub.dev install command until its version is verified.
Expo crypto
Run npx expo install expo-crypto, import AnyOAuth from @anyoauth/expo/native,
and provide that crypto module to the client. The native entry does not require
Web Crypto in Hermes and does not fall back to insecure randomness.
Verify a release
The SDK catalog is generated from verified publication metadata. GitHub hosts versioned source archives and checksums; the AnyOAuth website does not host SDK downloads. Each pinned repository README includes native build/conformance instructions. Tests use local fixtures, never production credentials.