Integration is absolutely key for powering APIs, to bring data together from across an organization to where it needs to be, in the format it needs to be in; the APIs then expose that data to where it needs to go to achieve that business value.
There are various ways of creating or obtaining APIs for use in IBM App Connect.
- Create flows for an API
You can create flows for an API (also referred to as an API flow). Each API flow is the implementation for an API operation (like ‘GET order’ or ‘POST order’) that is typically invoked from mobile and web applications.
An API flow contains a request, one or more actions for an application or API, optional toolbox nodes for specialized data processing, and a response. The request uses a model that you define to request the creation, replacement, or retrieval of data objects in your applications or APIs. When the request is submitted, each target application or API performs its action, and then the flow returns a response that either confirms that the actions were successful, or returns the data that was requested. You can define multiple flows for an API and then expose these flows as API operations.
- Add APIs to the App Connect catalog
You can add APIs to the App Connect catalog by importing OpenAPI documents that contain API definitions. All APIs that you import are added to the APIs tab of the App Connect catalog and are tagged with an ‘imported’ label .
If using IBM App Connect on IBM Cloud, all APIs that are shared in your IBM Cloud organization using native API management are also automatically added to the APIs tab of the App Connect catalog.
- Access an API from an HTTP invoke action in an event-driven flow
You can use App Connect to pass key data from an app into an HTTP ‘invoke’ action that calls out to an HTTP endpoint of an API, and then pass data returned from the HTTP response into other apps â€“ automatically, in real time.