Configuring API Callback Processor Settings
webMethods API Gateway provides asynchronous form of API support for REST APIs with its capability of defining the callback component with the supported method parameters while creating a REST API.
You must have the Manage general administration configurations functional privileges to configure callback processor settings.
Configure the API callback processor setting All API callback requests so that webMethods API Gateway accepts all the requests from the client that contain the callback request URL and wraps the requests with its own URL before routing them to the native API. This lets webMethods API Gateway track the requests that the client sends to the native API and the callback messages that are sent by the native API to the client. In addition, you can use the settings Allow HTTPS access only and Process only allowed IPs requests to avoid any external threats in case an unauthorized user tries to access the protected resource. You can configure webMethods API Gateway to enforce any of the response processing policies that suits your needs on the immediate responses as well as the callback requests being sent from the native API to the client.
- For webMethods API Gateway destination the field name is callbackRequest, which is set to true.
- For the Elasticsearch destination the field name is isCallbackRequest, which is set to true.
- For all other destinations, API Portal, Audit Log, CentraSite, Email, JDBC, and Local log, the field name is isCallbackRequest, which is wrapped under the customFields column.
To configure API callback processor settings