Need Central Catalog of 3rd-Party APIs

Noah needs a single catalog where internal teams can discover what 3rd-party APIs the organization uses.

Persona Noah — Head of Integration

Type Brownfield

Frequency Ongoing

Themes Discoverability and Reuse

Take Control Of Your Signals — Become a Naftiko Design Partner Today!

Persona Story: Noah, the head of integration, needs a single catalog where internal teams can discover what 3rd-party APIs the organization uses.

Duplicate effort as multiple teams research and integrate the same 3rd-party APIs
Missed opportunities to leverage existing integrations and institutional knowledge
Unable to negotiate enterprise agreements without knowing full usage footprint

Capability specs explicitly declare external API consumption with base URLs, auth methods, and namespaces, creating a de facto catalog of 3rd-party API usage
Multi-source consumption with unique namespaces provides clear visibility into which external services are being used across capabilities
Backstage Integration surfaces registered capabilities in a web UI, giving teams a central place to discover what 3rd-party APIs the organization already integrates with
External bindings for secrets and tokens centralize how teams connect to 3rd-party services, providing a trail of which external APIs are in use

Naftiko Shipyard MVP (Second Alpha) would serve as a centralized registry where all 3rd-party API integrations are discoverable and shareable
Fabric capability discovery (Dec 2026) would enable organization-wide discovery of all capabilities consuming external APIs
Tech Radar plugin for Backstage (GA) would help teams evaluate and standardize which 3rd-party APIs are recommended, tolerated, or deprecated
Reference bridge capabilities (Beta) would provide pre-built integrations for common 3rd-party data formats, reducing duplicated effort