API7 Docs

Developer Portal Overview

Learn about the API7 Developer Portal, a platform for API providers to publish API products and for developers to discover, subscribe to, and consume APIs.

The API7 Developer Portal is a platform that bridges API providers and API consumers. It allows providers to publish API products and manage developer access, while giving developers a self-service experience to discover, subscribe to, and consume APIs.

Architecture

The Developer Portal consists of two components:

  • Provider Portal: Built into the API7 Dashboard, where administrators manage API products, portal settings, developer accounts, and subscription approvals.
  • Developer Portal: A standalone web application where developers browse APIs, create applications, manage credentials, and subscribe to API products.

Developer Portal (Standalone App)

Portal API (Control Plane)

API calls with credentials

REST API

Portal SDK

Publish auth config

API7 Gateway (Data Plane)

Data Plane Nodes

Provider Portal (API7 Dashboard)

Manage API Products,
Developers, Subscriptions

Portal Settings,
Tokens, SSO

REST API on port 4321

Database

Next.js Frontend

Backend for Frontend

Portal Database

API Provider

API Developer

Developer Portal (Standalone App)

Portal API (Control Plane)

API calls with credentials

REST API

Portal SDK

Publish auth config

API7 Gateway (Data Plane)

Data Plane Nodes

Provider Portal (API7 Dashboard)

Manage API Products,
Developers, Subscriptions

Portal Settings,
Tokens, SSO

REST API on port 4321

Database

Next.js Frontend

Backend for Frontend

Portal Database

API Provider

API Developer

The Provider Portal and Developer Portal connect through the Portal API. When an administrator publishes an API product with authentication requirements, the Portal API pushes authentication configuration to the gateway data plane. Developers then use their credentials to access APIs through the gateway.

Key Concepts

ConceptDescription
API ProductsCurated bundles of API services published for developer consumption, with associated documentation, authentication requirements, and subscription policies.
DevelopersUsers of the Developer Portal who discover, subscribe to, and consume APIs.
ApplicationsContainers that developers create to group subscriptions and credentials for a specific project or use case.
SubscriptionsRelationships between developer applications and API products that grant access to consume APIs.
CredentialsAuthentication tokens (API keys, basic auth, or OAuth clients) that developers use to authenticate API requests.

Use Cases

The Developer Portal supports three primary deployment models:

  • Internal API Portal: Share APIs within your organization. Developers authenticate using corporate SSO, and API products are scoped to internal services.
  • Partner API Portal: Expose APIs to trusted partners with controlled access. Use SSO or email-based registration with administrative approval.
  • Public API Portal: Offer APIs to external developers through a public-facing portal with self-registration and subscription management.

You can run multiple portal instances simultaneously, each serving a different audience with distinct API product catalogs and access policies.

Provider vs. Developer Workflows

AspectProvider (Admin)Developer
Access pointAPI7 DashboardStandalone Developer Portal
Key actionsCreate API products, manage developers, approve subscriptions, configure SSOBrowse APIs, create applications, subscribe to products, manage credentials
AuthenticationAPI7 Gateway user accountPortal-specific account (email, SSO, or SCIM-provisioned)
CustomizationNot customizableFully customizable (branding, theme, domain)

Next Steps