Flinks

The most common use case is using Flinks Connect to easily connect end-users to their banks and after extract the saved data using the API in cached mode, f...

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...

With the Tag feature, it's possible to mark a specific LoginId according with specific needs from different use cases. Here's an example of a flo...

  For clients who are connecting for the first time, implement this example flow. For all registered LoginIds, keep track on your end which one's...

To get authorized into an account, there are at least three elements you need; the institution, the username, and the password. With these elements, you can...

Even in cached mode it's still possible to receive a API response with the code 202 OPERATION_PENDING.   That is the case when there is still a...

For this particular flow to be possible via Flinks Connect is mandatory the use of the feature sync, as well the redirectUrl parameter. Instead of the usua...

In this article we demonstrated an example of the async flow where a processing time for an account takes more than 210 seconds.  Whenever the API conn...

There are two different ways you can get Authorize through a financial institution with Flinks. With the LoginId or with the Credentials. You can find more ...

 In this example we have a flow to retrieve the Income Verification from one specific linked account. We're going to use our dummy institution Flinks C...