API and Mapping
While creating APIs in the API Manager, sample request and response are provided. The keys entered in this sample are reflected in the Source and Destination sections in the Mapping configuration page
Last updated
While creating APIs in the API Manager, sample request and response are provided. The keys entered in this sample are reflected in the Source and Destination sections in the Mapping configuration page
Last updated
When an API is created in the API manager, a system is chosen for the API to be associated with. Also, sample request and response data are given while creating an API.
For more information, click here.
Now let us see how this API gets linked with the Mapping node
The API Call Handler is added to the Flow to make an API call to a system. Depending on the system chosen, you can select an associated API from the drop down list. Any newly added API from here will also be available in the list.
More than one API Call can be added in a Flow.
The Mapping Handler is added to link data from a source API to a destination API.
When a Mapping Handler is added to the Flow, you will be choosing two API's (a source and a destination) to map. Note that, only API calls made within the Flow will be available for the user to select from.
While adding a new Pipe, you are required to choose System Credentials. Credentials are directly related to a system.
Depending on the Credentials (System) selected, the Flows (with API calls to those systems - Step 2) will be populated in the drop-down list.
Depending on the Flow selected, the Mapping nodes will be displayed (only if Mapping handler is added in the Flow - Step 2)
If no Mapping Handler is added in the Flow, Mapping node will not be displayed
Click on Configure. The mapping Configuration window will open.
The Source API fields are populated from its sample response and Destination API fields are populated from its sample request provided in the API Manager page (From Step 1).
