Publishing & the developer portal

From spec to consumable product

Once a spec is agreed, publish it to Exchange as a versioned asset. From there it becomes discoverable and consumable through the developer-facing portal.

Exchange and the portal

• Exchange holds the asset: spec, docs, examples, dependencies, versions.
• The developer portal (and Anypoint Experience Hub for a richer, branded, multi-API developer experience) presents APIs to consumers — docs, try-it console, and the path to request access.

What a good API listing includes

• A clear overview and getting-started guide.
• Live, accurate reference docs generated from the spec.
• Examples and a try-it experience.
• Explicit versioning and support status.

Coaching note

An API is a product with consumers, not an endpoint. Guide customers to invest in the portal experience the way they would a product page — because adoption follows clarity. Experience Hub is where a customer graduates from "we have APIs" to "we have an API program others want to use."