Documentation Index
Fetch the complete documentation index at: https://docs.tight.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Tight integrates directly with Snowflake to periodically upload raw accounting data to your own Snowflake data warehouse. By pushing data into your Snowflake infrastructure, Tight eliminates the need for your data team to build direct connections to the Tight API, allowing your team to work in the data stack they’re already using. Data is exported in Parquet file format on daily, weekly, or monthly intervals, including bank linkage data, invoices, lifecycle events, and transactions. Learn more about available data types and use cases in the Data Lakes guide.Create a Snowflake Managed Stage
If you haven’t done so already, create a Snowflake account and create a Snowflake Managed Stage where Tight will upload your data. You can name this stage anything you’d like; “TIGHT_DATALAKE_UPLOADS” is used for the examples shown below.

Create Key Pair Authentication Keys
Next, generate key pair authentication keys for secure authentication to your Snowflake account. From the command prompt, execute the following commands:rsa_key.p8 and rsa_key.pub files securely for use in later steps.
Create an Upload Role
Create a dedicated role for Tight to use when uploading data to your Snowflake warehouse. For example, name itTIGHT_UPLOADER_ROLE:

Grant Role Permissions
Grant the necessary permissions to theTIGHT_UPLOADER_ROLE:
Grant USAGE to Database:


TIGHT_DATALAKE_UPLOADS):

Create a Service User
Create a service user using Snowflake SQL. Service users with RSA authentication cannot be created through the Snowflake UI, so you’ll need to execute SQL commands. Using the public key fromrsa_key.pub that you generated earlier, execute the following SQL statement:

Grant Role to Service User
Grant theTIGHT_UPLOADER_ROLE to your TIGHT_UPLOADER_USER:

Securely Share Access with Tight
Contact Tight directly at api@tight.com for instructions on how to securely share:- Snowflake account identifier (e.g., GSX***-****)
- Database name
- Schema name (typically PUBLIC)
- Stage name (e.g., TIGHT_DATALAKE_UPLOADS)
- Service user name (e.g., TIGHT_UPLOADER_USER)
- RSA private key file (
rsa_key.p8)