Discovr uses a two-credential authentication system to keep your app secure. The SDK handles credential management automatically—you just call API methods.Documentation Index
Fetch the complete documentation index at: https://docs.discovr.media/llms.txt
Use this file to discover all available pages before exploring further.
Two credentials, one system
Discovr works with two credentials that handle different parts of your app: Identity credential — Long-lived account credential (90 days). Stored securely by the SDK. You use it to manage profiles and sign out. Session credential — Short-lived browsing credential. The SDK creates it automatically when you select a profile, refreshes it as needed, and includes it with every API request. You never manage it directly. The SDK handles all credential management automatically—refresh, rotation, storage—you just focus on your app’s UI and features.Code samples use TypeScript, Kotlin, and Swift tabs. Switching languages in one code
group switches all matching groups across the guide pages.
Choose your flow
Web Sign-in Flow
For web apps and mobile browsers. User redirects to login, then returns to your app with a
refresh token.
Device Code Flow
For TVs, IoT, or second-screen login. User sees a code and QR on device, signs in elsewhere.
Visual overview
After sign-in
Once you have an identity credential, you’ll:- Select a profile — Each device user gets their own profile with separate recommendations
- Session is ready — SDK creates a session credential automatically when you select a profile
- Call the API — Use
DiscovrClientmethods (for examplecreatePage()); SDK handles the session automatically
Related SDK reference
Authentication and session APIs (signatures and examples in SDK Reference):- signInWithPopup · signInWithWebAuth · signInWithDeviceCode · handleRedirectResult
- selectProfile · switchProfile · signOut
- onAuthStateChanged · onSessionRefreshed · isSignedIn
- getProfiles · createPage
Sessions, Profiles & Sign Out
Select profiles, understand session tokens, and sign out the current device.
Profiles
Overview, picker UI patterns, and create / edit / delete with the SDK.
Need help?
Error Handling
Map error codes to developer actions. Handle sign-in failures, token expiry, network errors.
Security Best Practices
Don’t log tokens. Use HTTPS. Let SDK handle secure storage. Your responsibilities and SDK’s.
Next: Start with Web Sign-in Flow or Device Code Flow depending on your platform.