Skip to main content
Many banks and FinTech companies leverage Finicity for transaction aggregation, cleansing and categorization. Tight lets you build directly on top of your Finicity integration.

​
1. How it works

Through Tight’s Finicity integration, your user’s transactions are pushed into Tight immediately after Finicity has cleansed them. All of those transactions are then run through Tight’s proprietary algorithms, which leverage the user’s business type, accountant best practices, and the behavior of similar businesses within the Hurdlr app’s 700k+ users. That data can then be instantly leveraged throughout Tight’s APIs, which include expense categorization, tax categorization, financial reporting, tax estimates, tax reporting, tax filing, and many other features. You can also quickly and easily embed Tight’s white-labelled UI into your product, which automatically leverages the data from your Finicity integration.

​
2. Pushing transactions into the Tight API

Once you have received your cleansed transactions from Finicity, you can simply POST those transactions into the Tight API: 
curl \
  --request POST \
  --url https://sandbox.hurdlr.com/rest/v5/banks/transactions \
  --header 'Authorization: Bearer ${access_token}' \
  --header 'Content-Type: application/json' \
  --data '{
    "transactions": [
      {
        "apiTransactionId": "1123144594",
        "date": "2020-08-27 00:00:00.000",
        "amount": 500.39,
        "description": "United Airlines",
        "finicityCategoryName": "Air Travel",
        "apiAccountId": "459043850",
        "apiAccountNo": "5435",
        "apiAccountName": "Citi Premier® Card",
        "apiAccountType": "CREDIT",
        "apiInstitutionId": "Citi"
      }
    ]
  }'
On each transaction, you can provide the following attributes:
FieldDescriptionFormat
apiTransactionIdId of the transaction record in your DBAny string
dateDate that the transaction was incurredyyyy-MM-dd'T'HH:mm:ss.SSSZ
amountTotal value of the transaction; deposits should be positive and withdrawals should be negativeNumeric, with 2 decimal places
descriptionTransaction description from FinicityAny string
finicityCategoryNameTransaction category from FinicityAny string
apiAccountIdId of the transaction’s bank account in your DBAny string
apiAccountNoMask of the user’s bank account, often the last 4 digits of the account number (used in reporting)2-4 Alphanumeric characters
apiAccountNameDisplay name for the user’s bank account (used in reporting)Any string
apiAccountTypeType of the user’s bank accountMust be one of the following: “CREDIT”, “DEPOSITORY”
apiInstitutionIdName of the institution that the transaction originated from (used in reporting)Any string

​
3. Next Steps

After your user’s transactions are pushed into the Tight API, all of Tight’s Expense Tracking and Income Streams features will immediately become available to your user, both in the Embeddable User Interface and via API. Whether you are building your own UX from scratch or have some existing functionality that you are looking to enhance, the Tight API team is here to help. Don’t hesitate to email us at api@tight.com, and we would be glad to help you create and complete the best next steps for your product and vision.