Skip to main content
Put simply, data attributes are outputs of organized and transformed transactional data. You’ll receive enriched data, through attributes, to gain a better understanding of your client’s behaviour without having to deal with categorization, cleaning, or any of the tedious tasks that are typically required when working with raw data. Flinks offers several attributes packages that you can choose from. We structure these packages in tiers, based on the data that you want to receive. For more information about our Enrichment solution, please speak with your Flinks Representative. Flinks can return a wide variety of data from the accounts we are connected to, including the following:

​
Personal information

  • Name
  • Address
  • Civic Address
  • City
  • Province or State
  • ZIP or Postal Code
  • PO Box
  • Country
  • E-mail
  • Telephone Number

​
Account information

  • Title
  • Balance
  • Transit or Routing Number
  • Institution Number
  • Account Number
  • Category and Type

​
Transaction history

  • Transaction Date
  • Transaction Description
  • Credit or Debit Amount
  • Current Balance

​
How it works

Attributes can be put together to gain a better 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 below. If you have a subscription to a specific use-case, these are the endpoints 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 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 3 API calls to pull back Attributes—You should follow the below API call flow to ensure no errors:

An important note:

The previous call to /GetAccountsDetail must be completely finished before initiating the series of calls below, 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.