Developer Platform & API Ecosystem Management

BC-4270 Level 1 Software & Technology 188 providers 322 API surfaces 88 rated strong or better

Public APIs, SDKs, developer portal, developer identity, API consumption governance, partner apps, software-marketplace listings, and outbound webhook subscriptions for the SaaS ecosystem.

Developer Platform & API Ecosystem Management (BC-4270) is a level-1 business capability in the Software & Technology model. The catalog holds 322 API surface(s) from 188 provider(s) that can perform some part of it, 88 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Authorities this capability cites

Cited by the capability model itself. These frameworks are referenced, never redistributed, and citing one does not imply its owner endorses this listing.

Sub-capabilities

Public API Lifecycle Management BC-4270.10

Specification, versioning, and deprecation of public APIs exposed to external developers.

8 providers, 23 API surfaces

SDK & Client Library Management BC-4270.20

Generation, language coverage, and sample maintenance of SDKs and client libraries that wrap public APIs.

2 providers, 2 API surfaces

Developer Portal Management BC-4270.30

Documentation, interactive references, and onboarding flows that help developers integrate with the platform.

3 providers, 11 API surfaces

Developer Identity & Credential Management BC-4270.40

Issuance and stewardship of developer credentials, OAuth clients, and federated developer identity.

60 providers, 78 API surfaces

API Consumption Governance BC-4270.50

Quotas, rate limits, usage analytics, and mapping of API consumption to commercial plan tiers.

12 providers, 22 API surfaces

Partner App Programme Management BC-4270.60

Stewardship of third-party partner applications including listing, certification, and revenue sharing.

2 providers, 3 API surfaces

Software Marketplace Listing Management BC-4270.70

Listing and stewardship of the SaaS offering on third-party software marketplaces and cloud marketplaces.

3 providers, 5 API surfaces

Webhook & Event Subscription Management BC-4270.80

Lifecycle of outbound webhook subscriptions, event schemas, and delivery reliability.

136 providers, 174 API surfaces

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Developer Platform & API Ecosystem Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →