Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.flinks.com/llms.txt

Use this file to discover all available pages before exploring further.

Attributes automatically transform the raw transactional data (that you get through the /GetAccountsDetail endpoint) into real-time, actionable insights. Each data attribute reveals an aspect of your clients’ financial profile and consumer behaviour. Put simply, data attributes are outputs of organized, cleansed, and transformed transactional data. You get the benefits of using enriched data to feed your models and gain a better understanding of your clients behaviour—without having to deal with categorization, cleaning, or any of the multitude of other tedious tasks that arise when working with raw data. They can be put together like building blocks to create a far superior understanding of your clients behaviour. We currently provide use-case specific packages of Attributes, as well as custom packages. Important note on use-case endpoints : Each of the use-cases are detailed via their own /{use-case} endpoint. If you have a subscription for a specific use-case, these are the endpoints that you should use. You will not be able to call the /GetAllAttributes or /Attributes endpoints. Important note on other endpoints : If you have a subscription to our full library, you are able to choose between the use-case endpoints, the /GetAllAttributes endpoint, and/or our customizable /Attributes endpoint for your specific requirements. Important flow for integration : You will have to set up an additional three API calls to pull back Attributes—You should follow the API Call Flow below to ensure no errors.

A note on the API Call Flow

The previous live call to /GetAccountsDetail must be completely finished before initiating the below series of calls, otherwise you may receive a 202 OPERATION_PENDING error.
  1. Make a call to /Authorize with the parameter MostRecentCached:true to exchange your loginId for a new requestId and open a session.
  2. Make a call to /GetAccountsDetail with the parameter requestId to pull back transactional data ready for analysis.
  3. Set up your job to call the specific /Attributes endpoint required only when the previous /GetAccountsDetail call has been successfully completed.

Operations accounts only

Operations is the only supported value.
You can test your integration directly from the API playground above, or by using the Toolbox sandbox credentials to make API calls against the test environment.