Sign in and manage profiles

🔐 App/Shop sign-in and authorization are available in the current release. Partner Center sign-in uses OAuth; the active profile provides protected authorization for supported App, Shop, sandbox, and DevAPI workflows. Profile metadata is stored locally, while access and refresh tokens are kept in macOS Keychain or Windows CurrentUser DPAPI and are not printed by status commands.

tts_open_toolkit auth login

The CLI opens Partner Center authorization in your browser and returns to a localhost callback after approval.

tts_open_toolkit auth status --json
tts_open_toolkit auth list --json

tts_open_toolkit auth login --add --profile work
tts_open_toolkit auth list --json
tts_open_toolkit auth switch work --json

The active profile determines which protected OAuth session is used. Select the intended App/Shop context before running a supported API, sandbox, or DevAPI workflow.

tts_open_toolkit auth basic-info --json
tts_open_toolkit app list --json
tts_open_toolkit sandbox list --json

tts_open_toolkit auth logout --profile work --json
tts_open_toolkit auth logout --all --json

💡 Never paste OAuth tokens, authorization codes, App Secrets, PKCE verifiers, or Partner Center cookies into an AI prompt. If authentication state is unclear, run tts_open_toolkit auth doctor --json.

---

Was this page helpful?

Tell us what worked, what was unclear, or what should be added. TTS Open Toolkit Feedback Form