Use the Developer Console
The Developer Console is the tenant-scoped catalog of every mounted backend operation. This journey reads the console policy, finds operations in the catalog, and exports them to Postman for repeatable execution.
Complete first: Onboard a tenant.
Steps and why they come in this order
| Step | Why here |
|---|---|
| 1. Read the console policy | The policy decides whether the console is enabled and how users sign in. Read it before sending users to a console they cannot open. |
| 2. Discover operations and their contracts | Every other journey names operation ids. The catalog confirms they are mounted for this tenant before you depend on them. |
| 3. Export to Postman | Export comes last because the collection reflects the catalog you just confirmed. |
What the console is not
The console executes backend REST operations through a same-origin gateway with a service token from its login and STS helper. It is not a wallet: wallet authorization, credential acquisition and presentation belong to a separate holder client. A missing operation in the catalog is an exposure boundary (tenant, license, capability or policy), not a malformed request.
Deeper reference
Developer Console describes sign-in, the API reference views, Test Request and result interpretation in detail.
Next
Return to the Platform foundations overview.