Haapi SDKs#
The Curity HAAPI client SDKs are layered libraries for iOS, Android, and React Native. They handle authentication, attestation, token management, and the HAAPI flow protocol so that mobile applications integrate with the Curity Identity Server without re-implementing the wire protocol.
The documentation is organised by layer (UI → SDK → Driver) and cross-cut by concept. Concept pages explain what a feature is; layer pages explain how to wire it up; How-To pages walk specific user goals end-to-end.
Where to start. New to the HAAPI SDKs? Read Getting Started — Overview , then use Choose Your Layer to decide between the UI / SDK / Driver Layer (React Native always uses the SDK Layer), then jump to your platform’s iOS , Android , or React Native quickstart.
Sections#
Getting Started
Overview, layer-choice decision tree, and platform quickstarts.
Concepts
Cross-cutting ideas — attestation, token binding, DPoP, DCR, error handling, observability.
Driver Layer
Lowest level — direct access to HaapiTokenManager and the HAAPI HTTP client on iOS and Android.
SDK Layer
Mid level — structured flow stepping and OAuth lifecycle. React Native’s only public surface.
UI Layer
Highest level — prebuilt, theme-able iOS UIKit and Android UIWidget screens.
How-To Guides
Task-driven recipes for token binding, DCR fallback, logging, error handling, risk assessment.
Platform Notes
Per-platform setup quirks — AutoFill, deep links, manifests, simulator behaviour.
Upgrade Guides
Migration notes for cross-cutting changes and per-framework major versions.
Reference
Deep links to the auto-generated API reference sites (DocC, KDoc, TSDoc) for every framework.