The processing time for retrieving bank information can vary depending on the bank and the amount of data an account have. When the API faces a long request, you'll have to interact with it in an asynchronous way.



We have an example of how the asynchronous flow looks like with our Flinks Capital test account. You can also make this test by yourself!


 


We start the usual flow with an Authorize call:



Answer any MFA if prompted and finish the Authorize flow:


Now you can do the GetAccountsDetail with the RequestId received from the successful Authorize call.
If your request takes longer than 210 seconds after making a GetAccountsDetail call, you will receive a 202 OPERATION_PENDING code, and from then on you will have to call the async endpoint GetAccountsDetailAsync in a long polling fashion.



Now we call the async endpoint GetAccountsDetailAsync. We suggest an interval of 15 seconds, but that could depend on your integration.


We receive again the code 202, which means our request is still processing. We have to keep calling GetAccountsDetailAsync.



Now we receive the code 200, meaning that your request is complete. We also get all the information retrieved from the account in the response.


 


Important note: we recommend having a 30 minutes timeout to stop calling the async endpoint because of a special case described here.



You can find more information about the GetAccountsDetailsAsync in our API documentation.