← Help home

Partner registry and routing

Last reviewed: 2026-04-27 · Owner: Product & Engineering

Goal

Load and interpret the partner list for a tenant and understand how registry entries relate to routing and launch.

Prerequisites

  • Tenant id such as tenant_alpha (synthetic).
  • Read access to GET /v1/admin/tenants/{tenant_id}/partners per your role.

Steps

  1. Open Partners in the admin console (/console/partners).
  2. Enter the tenant id and load the registry; confirm partner_key, enabled, and protocol_mode.
  3. Use Partner detail for governance summaries including federation posture (read-only hints).

Verify

  • Registry output matches expectations from your integration agreement (still using synthetic ids in docs).
  • Disabled partners do not appear in launch paths you expect to be active.

If it fails

Confirm tenant scope, actor role, and that the partner key spelling matches SPEC-004. Capture correlation ids from API errors, not secrets.

Further reading