跳至主要内容

API Token Migration Auditor

Turn API Token Usage Reports into a practical OAuth migration workbench.

無評級

留下評論

相容於

Support

開發者

TCYM

About this app

Find the integrations behind observed API-token activity, then plan the OAuth work

Import multiple official API Token Usage Report CSVs and review observed activity, coverage, gaps, token use, endpoint groups, and caller fingerprints.

Create named migration targets and manually assign caller fingerprints after confirming the service boundary with its owner. IP and user-agent differences are signals, not proof; possible shared tokens are never split automatically.

Build an integration-level OAuth Migration Blueprint with observed endpoints, least-privilege scope candidates, suggested client allowed scopes, flow questions, token renewal notes, and attribution considerations. Unknown and partial mappings remain visible for manual review.

Track discovery, design, implementation, cutover, and verification with an integration checklist. Export a versioned migration plan or safe baseline. Import later reports to compare legacy activity with the baseline. A lack of observed API-token activity is not proof that an OAuth replacement is working.

Your CSVs and migration workspace stay in browser memory. The app does not connect to Zendesk APIs, request credentials, upload data, or use an external backend, persistent browser storage, telemetry, analytics, or AI.

This is observed-activity decision support. Infrequent jobs may be absent; truncated token identifiers do not reveal original credentials; caller fingerprints do not prove distinct integrations; scope and flow suggestions need owner review. The app does not create OAuth clients, change credentials, disable API tokens, or migrate integrations automatically.

應用程式詳情

如何安裝

  1. Install API Token Migration Auditor and open it from Support navigation.

  2. In Admin Center, generate an API Token Usage Report and select its CSV in the app. Each report covers a seven-day window or up to 500 MB. Generate reports every few days to build a rolling 30–60-day history.

  3. Review Observation Coverage and Tokens. In Integrations, create named targets and manually assign caller fingerprints after confirming the service boundary with the integration owner.

  4. Complete the OAuth questions, review scopes and allowed scopes, then use Migration to track implementation and cutover.

  5. Export a Safe Baseline before migration. Later, import a new report and compare in Verify. A lack of observed legacy activity is not proof that OAuth is working.

No API token, OAuth credential, Zendesk subdomain, or account setting is requested.

留下評論

與其他Zendesk社群分享你的經驗

.zendesk.com