Updates and improvements to Teal
financial_account_type on ledger templates.entries_start date.Developers can now use the expand parameter to request data of nested resources. For example, a Journal Entry object has several line entries; by using the expand parameter, you can request the full Line Entry objects using a single request. Expandable requests are noted in attribute descriptions throughout the API reference.
Read more about expanding responses here.
We have added the ability to create instance-level categorization rules. This allows you to give end users the ability to set their own custom rules that are specific to their business.
Read more about our categorizer here.
Every API response is now accompanied with standard rate limiting headers. Use these values to gauge how many requests can be made before reaching the limit.
In addition, the Refresh Ledger Transactions endpoint has an additional rate limit of 2 requests/minute. Read more in the docs.
name when Retrieving an Instance.instance_id when Retrieving Plaid Link Statuses.name or -name when Listing all Intances.You can now define Instance-level rules to apply Tags to Transactions automatically. This allows you to build advanced workflows and reduce the amount of time spent your customers spend tagging Transactions. You can create Tag Rules using the same expression language as categorization rules through the API. Read more about crafting categorization expressions and Tags or explore the Tag Rules Endpoints.
tag_idstart_date and end_date to transaction endpoints
Tags give your users to the ability filter their accounting reports by customizable groups, offering a more detailed and granular view of their business. Whether tracking profitability by job, assessing performance by location, or managing fund tracking, Tags provide a flexible solution for various segment tracking use cases.
An instance needs a tier 3 subscription in order to filter their reports using tags.
Read more about Tags here.
categorization_method attribute to the Transaction object. This attribute can be used to enable more sophisticated Transaction Review workflows
We have added a dashboard to the developer portal to configure and manage your Teal webhooks. We send currently webhooks events to inform you of changes to your Plaid-linked ledgers and will be adding webhooks for other data integrations and relevant endpoints in the future. Read more about our Plaid integration and configuring webhooks here.
starting_debit_balance was renamed to starting_cash_balanceending_debit_balance was renamed to ending_cash_balancestarting_balance and ending_balance keys:
debit_balance was renamed to cash_balancetotal_debit_amount was renamed to total_cash_balancecash_flow_ledgers keys:debit_amount was renamed to net_cash_flowtotal_debit_amount was renamed to total_net_cash_flowdebit_amount was renamed to amount
We have added a review_status field to the Transactions object. Transactions are now created with review_status = unreviewed, and you can update this status as you see fit. For example, you can use review_status to implement a workflow for your users to review and confirm Transaction categories that have been assigned by the Categorizer. Click here to view our guide on building this core accounting workflow.
We have added a new categorizer that selects a category based on similar transactions that have previously been categorized by either rules, AI, or the user. Over time, as more transactions are categorized within an instance, this categorizer becomes more effective.
Developers
Company