Overview
These ideas appear throughout the portal. Understanding them makes it easier to navigate Home, APIs, My Applications, My Teams, and Admin. Each card below is a short, focused explanation of one concept.
A configured connection from the portal to an API platform — test vs. production, and why everything you see is scoped to one.
Apigee, Gravitee, and Azure — the gateway providers an environment can connect to.
Consumer teams vs. backend teams, and how membership works.
Organisation-wide access patterns that tie who to which APIs.
Your client registration for calling APIs — credentials plus subscribed products.
Published API products for the current environment, and how consumers and producers relate to them.
Canonical OpenAPI plus per-locale overlays applied when someone reads the spec in another portal language.
Consuming vs. producing users, and the main role types the portal recognises.
Why menus and options differ between accounts and organisations.
How this fits together
- Pick the correct environment (and therefore platform) in the header.
- As a consumer, create or use applications and teams, and subscribe applications to APIs.
- As a producer, work with backend teams and publishing flows so products appear in the catalog; permission groups align access on the gateway side.
- Administrators configure environments, permission groups, and other org-wide settings.
Related topics
- Getting started — a tutorial that puts several of these concepts to work
- Reference — field-by-field and screen-by-screen detail for every area mentioned here