Product

API developer portal features
from first spec to release.

API Portal supports an API from its first spec to its retirement. The platform covers the daily work of API teams, governance controls access and workflows, and the enterprise features take the portal into organizations with many business units.

app.api-portal.io/catalog
RESTv3.0
Payment API
GraphQL
User Service
AsyncAPI
Event Stream
RESTBeta
Search API

// Workflow

How does a spec become an API teams can use?

Each step belongs to its own feature, and every step builds on what the previous one produced.

1

Upload the spec

You upload an OpenAPI, AsyncAPI, or GraphQL spec or deploy it from your pipeline with the CLI.

2

Find it in the catalog

The API catalog records the spec with its owner and version, so other teams can find it through search.

3

Try it in the explorer

The spec turns into interactive documentation where consumers send requests right in the browser.

4

Version and review

The linter checks every spec against your rules, and the version diff flags breaking changes before release.

5

Grant access

Roles and business groups define who can see and use an API.

Getting started with API Portal →

// Platform

The platform for everyday API work

Six features built around the spec, from the catalog to the linter in CI.

// Governance

Governance for access and workflows

Two features decide who can see an API and how APIs work together.

// Enterprise

Enterprise for many teams and brands

Large organizations usually need more than one portal, and often more than one brand.

// Formats

Eight spec formats in one catalog

REST, events, SOAP, OData, gRPC, and GraphQL sit side by side in one catalog, so developers find every interface through the same search.

OpenAPI and Swagger

OpenAPI 3.0, 3.1, and 3.2 plus Swagger 2.0. Our guide shows how to move older specs to 3.x.

AsyncAPI

Event-driven interfaces such as Kafka or MQTT streams, in AsyncAPI 2.0 through 2.6, 3.0, and 3.1.

Arazzo

Workflows across several APIs, described in Arazzo 1.0 and 1.1.

RAML

Existing specs in RAML 0.8 and 1.0 stay usable in the same catalog.

SOAP / WSDL

SOAP services from WSDL 1.1 and 2.0, with SOAP 1.1 and 1.2.

OData

OData 4.0 and 4.01 as CSDL XML or JSON, plus older services from 1.0 to 3.0.

Protocol Buffers and gRPC

gRPC services from proto2, proto3, and Editions 2023 and 2024.

GraphQL

GraphQL schemas in the same catalog as REST and events.

// FAQ

Frequently asked questions about the features

Our team is happy to answer anything else in a call.

Contact sales
There are five at its core. A catalog makes existing APIs discoverable, and interactive documentation lets consumers try them right away. Versioning and a version diff keep changes traceable, a linter keeps specs consistent, and access control decides who sees which API. Large organizations usually add separate portals for each business unit and a portal under their own brand.
The linter checks a spec against your rules before it is published as a new version. Versioning then assigns the SemVer version number and writes the changelog. The version diff shows which changes between two versions are breaking, so consumers can plan their migration.
Enterprise portals decide how many portals you run and who owns them. Each business unit gets its own portal with its own database. The white-label portal decides how a portal looks, from logo and favicon to name, theme, and domain.
The trial gives you the full feature set for 14 days. Starter covers up to 5 APIs with automatic documentation and 3 team members. Professional adds unlimited APIs, versioning with a changelog, access control, and 25 team members. SSO, SAML, and dedicated support come with the Enterprise plan. An SLA is available on request. Sales can walk you through pricing.

Try every feature with your own specs

The trial runs for 14 days with the full feature set and no credit card. A short message is all it takes to book a session with our team.