Asynchronous API integration

Hi Team,

We’re in the process of integrating an application, which is asynchronous in nature. There is a common API call, which will generate the automation ID, this will be the mandatory attribute for rest of the API calls (Actual API calls Create user, Get user, Disable User etc). Currently the actual calls have a delay of 6-7 mins, but it could be more.

what could be integration inputs for such kind of asynchronous API application. One approach can be webservice, but this delay will be going to handle. What are the best practice to integrate such application.

We have built delays into webservice rules. However, each running instance of a rule is going to remain running for each user until completion. If you have high volume, this could put load on your virtual appliance. If this becomes a problem, one option is to create a VA cluster and only assign this connector to the cluster. This will prevent other sources from getting bogged down. You will also probably have to adjust the timeouts for the source.

You might also find that it works better to take the processing offline from ISC. You could use an empty entitlement (ex. APIProvisioningGroup) to be able to use scripts to provision the downstream access.

Do you have any insights on using custom connector or mulesoft etc?

I would think that a custom connector would have similar issues as the processing will have to wait out at each step.

I don’t have any experience with MuleSoft.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.