SDK packages

Every Axowl SDK is on its public registry. Always install the latest version — the commands below do that by default, and the registry page shows the latest version and its changelog. Pinned versions in older examples go stale; check the registry before you pin one. Which package to pick and how to use it is on the SDK overview.

Package	Language	Registry	Install
@axowl/sdk	TypeScript (React)	npm	npm install @axowl/sdk
@axowl/sdk-backend	TypeScript (Node)	npm	npm install @axowl/sdk-backend
@axowl/sdk-core	TypeScript	npm	npm install @axowl/sdk-core
@axowl/sdk-analytics	TypeScript (browser)	npm	npm install @axowl/sdk-analytics
axowl-sdk	Python 3.9+	PyPI	pip install axowl-sdk
com.axowl:axowl-sdk	Java 17+	Maven Central	<dependency><groupId>com.axowl</groupId><artifactId>axowl-sdk</artifactId></dependency>
Axowl.Sdk.Identity.Abstractions	.NET	NuGet	dotnet add package Axowl.Sdk.Identity.Abstractions
Axowl.Sdk.Identity.Client	.NET	NuGet	dotnet add package Axowl.Sdk.Identity.Client
Axowl.Sdk.Integrity.Abstractions	.NET	NuGet	dotnet add package Axowl.Sdk.Integrity.Abstractions
Axowl.Sdk.Integrity.Client	.NET	NuGet	dotnet add package Axowl.Sdk.Integrity.Client
Axowl.Sdk.Integrity.Hashing	.NET	NuGet	dotnet add package Axowl.Sdk.Integrity.Hashing
Axowl.Sdk.Eventing.Abstractions	.NET	NuGet	dotnet add package Axowl.Sdk.Eventing.Abstractions
Axowl.Sdk.Eventing.Client	.NET	NuGet	dotnet add package Axowl.Sdk.Eventing.Client
Axowl.Sdk.Korean.Identity.Abstractions	.NET	NuGet	dotnet add package Axowl.Sdk.Korean.Identity.Abstractions
Axowl.Sdk.Korean.Identity.Client	.NET	NuGet	dotnet add package Axowl.Sdk.Korean.Identity.Client

Older .NET package names

Axowl.Sdk, Axowl.Sdk.AspNetCore and the Axowl.Enterprise.Sdk.* packages on nuget.org are an earlier generation and are not maintained. Use Axowl.Sdk.Identity.Client (and the other Axowl.Sdk.* packages above) instead.

Blazor end-user login: Blazor apps sign people in through the hosted login round trip — see Hosted login and .NET EndUser auth — and use Axowl.Sdk.Identity.Client for server-side token checks.

Which one do I need?

• Web front-end (React): @axowl/sdk. It brings @axowl/sdk-core with it — you rarely install the core package yourself.
• Your own API server: the backend SDK for your runtime — @axowl/sdk-backend (Node), Axowl.Sdk.Identity.Client (.NET), axowl-sdk (Python) or com.axowl:axowl-sdk (Java). All four verify the end-user token against your org’s JWKS the same way.
• Behavior analytics in the browser: @axowl/sdk-analytics — see the behavior analytics guide.
• Tamper-evident records (.NET): the Axowl.Sdk.Integrity.* packages — see Integrity.
• Event bus (.NET): Axowl.Sdk.Eventing.* — see Eventing.
• Korean identity verification (.NET): Axowl.Sdk.Korean.Identity.* — see Korean identity.

If an install fails

• 404 / “package not found”: check the exact name above — npm names are case-sensitive and scoped (@axowl/…).
• A version you expected is missing: a release can take a few minutes to appear (npm and nuget.org replicate; Maven Central syncs within about 30 minutes). Pin the version shown on the registry page.