Skip to main content
The Tight API connects to many data sources, with transaction feeds generally being the most important starting point. The Tight Embedded experience and API includes robust transaction feed integrations such that little to no development effort is needed to launch with your users’ most important data source fully connected.

​
How it works

Once you have registered your user with the Tight API, you can render the business owner experience for them; however they will need to see transactional data in order to get value. The Tight API makes this simple by providing native integrations with key data sources/aggregators for bank transactions (including Plaid and Unit), payments & payouts (including Stripe and Shopify), bills (including Melio), and payroll (including Gusto and Check). All your team needs to do is some basic administrative (non-developer) setup with the respective integration granting Tight with integration partner access. Take a look at our integrations docs for the full list of supported integrations along with detailed setup instructions.
In addition to Tight’s native data source integrations, you can also connect any custom data sources of your own by pushing transactions into the Tight API. This use case is most common for financial institutions that manage their own transactional data.

​
Automated reconciliation

As multiple data sources flow through the Tight API, Tight’s algorithms automate the reconciliation between those sources, saving your users time that would have otherwise been spent manually reconciling these transactions in legacy accounting systems. Invoice Payout example
  1. The business owner sends out 4 $1000 invoices to 4 clients.
  2. Those 4 invoices are paid via 4 separate credit card payments via Stripe. Stripe charges the user $25 in merchant fees for each of the 4 invoices.
  3. The user receives a payout from Stripe for 3890(3890 (4000 minus 100inmerchantfeesminusa100 in merchant fees minus a 10 contribution to Stripe Climate), also seen as a $3890 deposit into their checking account.
  4. The Tight API automatically matches the 4 invoices with the one payout, and creates expenses for the various merchant fees. Furthermore, the Tight Embedded experience nests these transaction line items neatly under a single payout row.
Note: Tight automatically creates the necessary accounting transactions under the hood (for accrual basis or cash basis, depending on the business’s accounting method) at each step of the above steps. Payroll example The business owner runs payroll at the end of the month.
  1. Gusto makes three separate withdrawals for the salaries, taxes, and benefits paid
  2. The Tight API automatically matches the 3 withdrawals with the one payroll run, automating all the necessary double entry accounting transactions under the hood for the accrual basis and cash basis accounting methods.

​
Alternative data sources

The Tight API can ingest data in many different ways, and the Tight API team has worked with many customer-partners across varying industries to streamline that integration process. For example, many Vertical SaaS companies have created their own invoicing systems, but use Tight to add payout reconciliation and full accounting. Reach out to our API team at api@tight.com for a custom implementation plan on how to integrate your existing data sources (e.g. homegrown invoicing) with external sources (e.g. Plaid bank account aggregation).