Marketplace & Storefront
The Marketplace is your organisation’s branded API storefront. It’s automatically generated from your API catalogue and serves as the discovery layer for both internal teams and external consumers.
What Consumers See
Section titled “What Consumers See”Every published API appears in the marketplace with:
| Information | Source |
|---|---|
| Name, description, business function | API metadata |
| Interactive documentation | Generated from OAS |
| SLA tiers and pricing | OpenSLA definition |
| Version history | Deployment records |
| Compliance score | Compliance service |
| Subscription options | Available tiers + self-service subscribe |
Branded Storefront
Section titled “Branded Storefront”Each tenant gets a branded developer portal at their own subdomain:
{tenant}.dev.apiway.netThe storefront inherits your branding and shows only the APIs you’ve published for external consumption. Internal APIs stay hidden.
Visibility Controls
Section titled “Visibility Controls”Producers control who can see each API:
| Visibility | Who Can See It |
|---|---|
| Team | Only the owning team |
| Functional Area | Teams within the same business function |
| Organisation | Everyone in the tenant |
| Invitation Only | Specific invited consumers |
| Partner | Partner organisations |
| Public | Anyone — visible in the marketplace |
Catalogue Architecture
Section titled “Catalogue Architecture”The marketplace is backed by the Marketplace API — a dedicated catalogue service:
- Core-service publishes API metadata via upsert (
PUT /v1/apis) - Marketplace API stores in MongoDB (single database, not per-tenant)
- Portals query with visibility filtering based on the caller’s JWT
- Anonymous access (external portal) only sees Public APIs scoped to the tenant
This separation means the catalogue is always fast and available — it doesn’t depend on core-service for reads.
External Developer Portal
Section titled “External Developer Portal”External consumers access your APIs through the developer portal:
- Browse — Discover available APIs by name, function, or capability
- Read docs — Interactive API documentation generated from the OAS
- Compare tiers — See what each SLA tier offers (rate limits, RU quota, pricing)
- Subscribe — Self-service subscription with automatic credential provisioning
- Manage — View active subscriptions, credentials, and usage
Version Guard
Section titled “Version Guard”When you publish a new version, the marketplace tracks the change:
- Non-breaking (minor/patch) — Existing consumers are unaffected, docs update automatically
- Breaking (major) — New version appears alongside the old one; consumers migrate at their own pace
- Deprecation — Old versions are marked with a retirement date; consumers are notified
Cross-Organisation Discovery
Section titled “Cross-Organisation Discovery”APIs flagged for external visibility are discoverable across tenant boundaries through the API Economy. Consumers from other organisations can subscribe — the OAS is copied into their tenant and goes through their own governance flow. Full tenant isolation is maintained.