Changelog
Flinks API Reference
< Back to Flinks

Attributes

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

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' behavior — 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’ behavior. 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 below. If you have a subscription to 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 full 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 (3) API calls to pull back Attributes - You should follow the below API Call Flow to ensure no errors.

(A note here: the previous live call to /GetAccountDetails 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 (as detailed below) required only when the previous /GetAccountsDetail call has been successfully completed.

🚧

A Note on the Above

Please ensure that you fully understand the information above, so that you know which section/API call to navigate too. If you have any questions, please feel free to reach out to [email protected]

For more information on how to test your integration and to see an example of what an API call can look like, refer to our help article.