API management checklist
A summary, with links, of the key tasks for managing APIs in IBM® API Connect.
| Task | Description |
|---|---|
| Configure your Catalogs | APIs are published to a catalog to make them available to application developers. The URLs for API calls, and for the Developer Portal, are specific to a particular catalog. By default, a sandbox catalog is provided for API testing, but you can create your own catalogs; for example, a production catalog for hosting APIs that are ready for full use. |
| Manage the membership of your Catalogs | You can add users to your catalogs, and assign roles and permissions to control their level of access. |
| Configure API security | You can configure OAuth providers for securing third-party website or application access to APIs. |
| Manage your Products | Move your Products through their lifecycle, from initially staging a Product to a catalog, through to publishing to make the Product version available to your application developers, and to eventual retiring and archiving. You can also display analytics information, and control who can see or subscribe to your Products. |
| Analyze your API usage | You can use IBM API Connect to filter, sort, and aggregate your API event data. You can present the results within correlated charts, tables, and maps to help you manage service levels, set quotas, establish controls, set up security policies, manage communities, and analyze trends. |
| Partition your Catalogs into Spaces for syndication | With the 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. |