1. How it works
The Tight API is able to ingest data from many different income streams, enabling you to easily provide your users with accurate tax calculations, financial reporting, and other accounting functionality. If you are not using Tight’s Plaid integration, in order for the Tight API to ingest your user’s business income data, you can simply push each income record, as it is earned, to the Tight API. The Tight API will take care of the rest. Tight allows you to track the income at the business-level, which is especially useful for self-employed folks who are earning income via multiple businesses. Optionally, the Tight Income Streams API lets you track income at the client-level, which enables very powerful financial reporting. Once you have your user’s self-employed and business income pushed into the Tight API, you can immediately start using all of Tight’s Tax Calculations, Financial Reporting, and other functionality.2. Adding self-employed or business income
If you are leveraging the Plaid integration for tracking income, please see the instructions on how to classify income transactions as business income. For any other business income streams from sources outside of the Plaid integration, you can simply add that income by making a POST call to the Tight API. You should update the following fields on a new JSON object when adding business income:| Field | Description | Format |
|---|---|---|
| date | Date that the revenue was deposited | yyyy-MM-dd or yyyy-MM-dd'T'HH:mm:ss.SSSZ |
| amount | Total value of the income | Numeric, with 2 decimal places |
| type | Whether the transaction was classified as Business or Personal | Must be one of the following: “BUSINESS”, “NOT_BUSINESS” |
| businessId | Id of the business that this should be assigned to | Numeric |
| clientId | Id of the client that this should be assigned to. Optional. | Numeric |
| description | Description of the income. Optional. | Any string |
3. Getting self-employed or business income
All self-employed or business income can be accessed in the list of revenues, via the /revenues endpoint:type field:
| Field | Description | Format |
|---|---|---|
| id | Id of the revenue record | Numeric |
| type | Whether the transaction was classified as Business or Personal | Must be one of the following: “PENDING”, “BUSINESS”, “NOT_BUSINESS” |
| date | Date that the revenue was earned | yyyy-MM-dd'T'HH:mm:ss.SSSZ |
| amount | Total value of the deposit | Numeric, with 2 decimal places |
| businessId | Id of the business that this was assigned to | Numeric |
| clientId | Id of the client that this was assigned to | Numeric |
| description | Description of the income | Any string |
| pendingRevenueId | Id of the associated pending revenue | Numeric |