Enabling Spaces in an IBM API Connect Catalog creates distinct partitions for managing the API lifecycle. This partitioning extends to all consumer-related entities and their management. Consequently, consumer organizations, the applications they register, the subscriptions those applications make to Products, the associated approval workflows, and the resulting analytics data are all scoped to and managed within a specific Space. This allows different teams to manage their own APIs and consumer communities independently within a single Catalog, providing a multi-tenant-like experience.

1. IBM API Connect v10.x Documentation

"Using Spaces in Catalogs": "When Spaces are enabled in a Catalog

API provider teams can manage their APIs and Products in a dedicated Space... allowing each team to manage its own API consumers... When an application developer signs in to the Developer Portal

they select which Space to work in. The application developer can register applications only in the Spaces that they have access to

and can subscribe only to the Products that are available in those Spaces." This confirms that consumers

applications

and subscriptions are space-specific.

2. IBM API Connect v10.x Documentation

"Viewing the analytics for a Space": "Analytics data is specific to a Catalog

and is partitioned by Space. You can view the analytics data for a specific Space." This confirms that analytics are also partitioned by Space.

3. IBM API Connect v10.x Documentation

"Managing consumer access to Spaces": "When Spaces are enabled

the Developer Portal is partitioned by Space. Application developers who are members of a consumer organization can be granted access to one or more Spaces." This directly links consumer management to the Space level.