Work with apps and sandbox accounts

Use authenticated App and sandbox context when a workflow depends on the developer account rather than documentation alone.

tts_open_toolkit auth login
tts_open_toolkit auth status --json

tts_open_toolkit app list --json
tts_open_toolkit app list --page-no 1 --page-size 20 --json
tts_open_toolkit app list --app-key <app_key> --json

Use app_key as an identifier in the workflow. Never request or print an App Secret.

tts_open_toolkit sandbox list --json
tts_open_toolkit sandbox list --region-code 840 --json
tts_open_toolkit sandbox endpoints --json

Inspect the endpoint catalog before running a sandbox operation:

tts_open_toolkit sandbox call account-basic-list --query region_code=840 --json

📝 Prompt to copy Using the active Partner Center profile, list the developer Apps and sandbox accounts available to me. Use JSON output, keep App Secrets and OAuth credentials hidden, and ask me to select the App and sandbox account before continuing. Then produce a readiness checklist for [BUSINESS SCENARIO] without making a write change. 💡 Sandbox account deletion is intentionally excluded from the CLI catalog. Do not construct a raw request to recreate it. Other sandbox operations can still be restricted by the OAuth allowlist or session type; report the returned authorization error instead of bypassing it.

---

Was this page helpful?

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