Using syndication in API Connect

With the IBM® API Connect syndication feature, you can partition your Catalogs into Spaces. Each Space is used by a different API provider development team and has its own set of management capabilities relating specifically to the APIs that the associated team publishes to that Space, enabling each team to manage their APIs independently.

When you stage or publish an API to a Catalog that has Spaces enabled, you specify the Space within that Catalog that you want to stage or publish to. However, application developers that access the Developer Portal for the Catalog are unaware of the Space partitioning of the Catalog and see the APIs as a coordinated offering.

Each Space has its own Product lifecycle management, subscription approvals, and analytics data. You use Space specific access control to restrict user access to each Space; for example, a developer in the Flights team is able to stage APIs only to the Flights Space.


A travel company, AcmeAir, has separate API provider development teams for each of the following areas of their business:
  • Flights
  • Hotels
  • Payments
  • User Profiles
They have an AcmeAir corporate Catalog, with its associated corporate Developer Portal. They partition their Catalog into separate Spaces, one for each development team.
diagram to demonstrate the travel company example

Spaces are described in detail in the following sections: