/Upload (Base Example)
Use the standard /Upload endpoint to upload transaction data and receive calculated attributes.
/Upload endpoint to run through some examples. If you are using any of the other endpoints listed above, the only difference is that you do not need to include an Attributes or AttributesDetail list.
A note on Use Case and All Attributes endpoints
TheCard and AttributesDetails objects within these requests are not required and, if provided, will be overwritten with the expected Attributes contained within the requested endpoint.Request Fields
Headers
Bearer Token (API secret key).
Path Parameters
Unique GUID provided by Flinks that grants you access to the environment.
Body
Tells the API to use a specific country model. Possible values include: - ca = Canada - us = United States
ca, us Contains the list of Attributes that will be returned for the given set of transactions. (JSON object)
The most recent balance for all transactions. Flinks uses this parameter to calculate the running balance if you are not passing the balance field in your transaction set or using OldestBalance.
If you are not using balance in the transaction set or OldestBalance, this parameter is required.
The oldest balance of all transactions. Flinks uses this parameter to calculate the running balance if you are not passing the balance field in your transaction set or using MostRecentBalance.
If you are not using balance in the transaction set or MostRecentBalance, this parameter is required.
List of Attributes that you require the underlying transactions to be returned from. Attribute names included here must also be included in the Attributes list.
Contains the previously formatted transactions (defined earlier in this documentation) that you are uploading to Flinks. (JSON array of objects)
Additional parameters that you want to include.