Getting started
Odynn Connect turns your users' airline, hotel, and card loyalty accounts into clean, normalized JSON — captured when they sign in on their own phone, so credentials never touch your servers or ours. Here is how it works, and how to integrate.
How Odynn Connect works
Odynn Connect turns a loyalty account your user holds — an airline, hotel, or card program — into structured JSON you can build on. Your user authenticates into the program on their own phone; Odynn extracts and normalizes the account; you read the result over the REST API. Three actors, three responsibilities: your backend creates sessions and reads data with an API key, the Odynn API orchestrates and normalizes, and the end-user's device runs the actual provider login — credentials never transit your servers or Odynn's.
Every session can be put in front of your user two ways. You choose per session:
| Path | What it is | When to use it |
|---|---|---|
connectUrl | Odynn-branded App Clip / Instant App, opened via Universal Link — no install needed. The launch URL comes back on the session response. | The path this guide teaches. Brandable, and the only path that will get fully silent refresh (coming soon). On desktop, render it as a QR code for the user's phone to scan. |
| Native SDK | The Odynn Connect Native SDK embeds the sync surface inside your own app. You hand the SDK the session id — it resolves the realtime transport itself, so your code never touches a transport URL. | Full UX control inside your own app, and the path available today. The Swift package resolves from its public repository in one Swift Package Manager line — see the Native SDK — iOS guide. |
One session, one device. The first device to connect — via either path — claims the session; a second connect is rejected. Mint a fresh session per attempt.
Choose an approach
Two ways to put the sync surface in front of your user. The iOS Native SDK is the path available today — you embed the flow inside your own app. White-label hands the user Odynn's hosted surface instead, and opens once the Odynn Connect app is listed on the App Store.
Native SDK — iOS
Embed the sync surface directly in your own iOS app with the Odynn Connect Native SDK (Swift) — your app hands off the session id and keeps full control of the UX. The path available today.
Read the iOS walkthroughWhite-label
Hand your user Odynn's hosted Connect surface — an App Clip / Instant App, no install, fully brandable, and the only path that will get silent refresh. It opens — and this label comes off — once the Odynn Connect app is listed on the App Store, because an App Clip is distributed from that listing.
Read the walkthroughNative SDK — Android
Embed the sync surface directly in your own Android app with the Odynn Connect Native SDK (Kotlin) — your app hands off the session id and keeps full control of the UX.
Android guide