Use cases — qonto organizations slug path inventory
Two concrete scenarios for the 2026-11-15 migration window. Local-only helper; not affiliated with the vendor. 官方 migrate 文强在换 URL；SERP 多为无关库存通识；缺跨仓路径字面量+Sunset 头并列盘点。不做银行控制台 SaaS。
Fintech API integrator: Clear all services of slug-based org paths before Nov 15
Who / role: Fintech API integrator acting as fintech-api-integrator in context qonto-org-slug-nov15-410. Expertise assumed: intermediate. Market frame: Qonto GET /v1|/v2/organizations/{slug} → 410 on Nov15 2026; replace with /v2/organization (banking API path domain).
Task: Clear all services of slug-based org paths before Nov 15 before deadline 2026-11-15. Vehicle is path-discovery-editor; output expected is cross-repo organizations/{slug} residue inventory + Markdown export.
Steps: Ripgrep → board rows → swap URL → header monitors → export. Use the home Hero to capture evidence locally, then paste the Markdown export into the migration ticket with official source URLs.
Result: No organizations/{slug} callers remain; ticket has residue export. Operators should keep a dated export attached to the change ticket, assign an accountable owner on every residue row, and re-open the official vendor documentation whenever a date or field name is unclear. Do not treat this local helper as a substitute for the vendor console or for production cutover approvals. Prefer verified primary sources over screenshots or chat summaries when communicating status to stakeholders.
Platform engineer owning shared Qonto client: Update the shared SDK and notify downstream repos
Who / role: Platform engineer owning shared Qonto client acting as fintech-api-integrator in context qonto-org-slug-nov15-410. Expertise assumed: intermediate. Market frame: Qonto GET /v1|/v2/organizations/{slug} → 410 on Nov15 2026; replace with /v2/organization (banking API path domain).
Task: Update the shared SDK and notify downstream repos before deadline 2026-11-15. Vehicle is path-discovery-editor; output expected is cross-repo organizations/{slug} residue inventory + Markdown export.
Steps: Patch client → publish → inventory downstream → close rows. Use the home Hero to capture evidence locally, then paste the Markdown export into the migration ticket with official source URLs.
Result: Shared client on /v2/organization; downstream signed off. Operators should keep a dated export attached to the change ticket, assign an accountable owner on every residue row, and re-open the official vendor documentation whenever a date or field name is unclear. Do not treat this local helper as a substitute for the vendor console or for production cutover approvals. Prefer verified primary sources over screenshots or chat summaries when communicating status to stakeholders.
Next: home tool · how-to · FAQ.