Exchange as the reuse hub
5 min · 50 XP · Read → Check → Complete
The library for your API program
Exchange is Anypoint's catalog of reusable assets: API specs, spec fragments, connectors, examples, policies, and templates. Reuse starts here — if an asset is not in Exchange, it will be rebuilt.
Asset types you coach teams to publish
- API specifications (RAML / OAS) — the contracts.
- Spec fragments — shareable pieces of a spec (data types, traits, security schemes).
- Examples and templates — accelerators for new APIs.
Making reuse real
- Tag and categorize assets so they are discoverable.
- Keep rich descriptions and examples — a findable asset nobody understands is not reused.
- Treat Exchange as the first place a team looks before building anything new.
Coaching note
Reuse is a cultural outcome, not a feature toggle. Guide the customer to make "search Exchange first" a team norm, and to celebrate the second use of an asset as the real win.
Check your understanding
1. What is Exchange's role in an API program?