Integration Guides by Track
Source:
en/tracks/index.md· Live: https://docs.1pass.dev/en/tracks LLM-sanitized: internal links absolutized, VitePress containers → admonitions, line numbers in the Jump-to Index reference this rendered file (1-indexed).
📍 Jump-to Index
- L28-L37: ## Common to every track
Integration Guides by Track
When you integrate logi (1pass) as an RP, follow only the one track that matches your case. The shared concepts (PKCE, scope, error codes, security model) point to the same pages from every track.
| Track | Who | Core |
|---|---|---|
| 📱 Mobile apps | iOS, Android, Flutter, and RN native app developers | Public client + PKCE, custom scheme redirect |
| 🌐 Web | Server-side web developers on Next.js, Rails, Express, and so on | Confidential client + server-held secret |
| 🔧 API · CLI | Backend, CLI, CI, AI agents, and webhook receivers | Device flow, MCP, webhooks, management API |
💡 Tip: Not sure which track you're on? If you're building something users install from an app store → mobile. If users reach it by URL in a browser → web. If it's invisible automation or machine-to-machine communication → API · CLI.
Common to every track
- Core concepts — App / Scope / Token / Sub
- Quickstart (5 minutes) — the whole flow with a single
curl - Registering apps — console UI walkthrough
- Choosing Public vs Confidential — the starting point for picking a track
- One RP per surface (best practice) — ⚠️ don't mix mobile and web in a single RP
- Security best practices
- Error codes