Skip to main content

​
Overview

Flinks built the Upload feature in order to allow your teams to leverage standardized, highly accurate data enrichment outputs (Attributes) regardless of the source of your financial data. This means that your team can submit external data to Flinks and receive the same insightful data that you already get from Flinks aggregated data.

​
Questions and answers about /Upload

​
What is /Upload?

  • An extension to Data Enrichment that allows you to submit external data to Flinks.
  • Allows your team to benefit from standardized, highly accurate data enrichment outputs on External Data (non-Flinks).
  • Via the Dashboard in a clean and simple UX.
  • Via the /Upload API by reformatting your data and uploading it (recommended).
  • Via the /Upload API by submitting data in an external format and allowing us to cleanse it for you.

​
What to expect in this section

​
What this documentation covers:

  • How to transform your data so Flinks can accept it.
  • How to choose the correct Upload endpoint for your requirements.
  • How to set it up and make API calls using external data.
Before continuing with this implementation, please reach out to our team to ensure that all required parameters are all set up on your instance.

Before getting started

The APIs detailed in this documentation should be viewed as an extension of the core Flinks Enrichment services. It is recommended that you understand the concept and use cases contained within Attributes before proceeding with this implementation.

Before getting started

You will need a secret bearer (authentication) token in order to use any of the /Upload API endpoints. If you do not have one already, contact your Flinks Representative to have one issued based on your private instance.

Note on unformatted data

This documentation will not detail how to submit data directly from another provider. If you plan on using a JSON file directly from another provider without reformatting first, please reach out to our team for information on how to do so and the API schemas we currently support.