Retrieve a Transaction from a Ledger
Returns a single Transaction via the ledger ID. Deprecated, use source account endpoints.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Headers
The Teal instance ID
Path Parameters
The Ledger ID.
The Transaction ID.
Query Parameters
Comma-separated list of Transaction expand paths.
ledger, line_entry, journal_entry, opposing_line_entries, opposing_line_entries.ledger, transfer, transfer.matched_transaction, transfer.matched_transaction.ledger, transfer.from_journal_entry, transfer.to_journal_entry Response
The unique ID of the object. This is used as an idempotency
key to prevent duplicates. This is manually set as part of the create
transactions request. If the transaction is created via a data integration,
Plaid for example, it will be set to the transaction_id to enforce
idempotency with the data source.
The value of the transaction in decimal dollar cents.
The UTC datetime that the Transaction was created. This
will never be before an Instance's entries_start date. When importing
transactions, transactions whose datetime is before the Instance’s
entries_start date will be skipped. Other transactions will be processed
as normal.
An arbitrary string on the object, useful for displaying information to the user.
Indicates if the corresponding journal entry and
line entries for the transaction have been have been created. deleted
indicates that the transaction is posted but the corresponding journal entry
and line entries have been deleted.
not_posted, posted, deleted Indicates if the transaction has been reviewed. See the reviewing transactions for steps on how to use this.
unreviewed, reviewed The ID of the transaction source account where the transaction is stored.
Whether the transaction is a non-business personal transaction.
Arbitrary structured information about the transaction. This could be location of the transaction to display to the user or vendor information to use as part of a Platform or Instance categorization rule. Teal does not use metadata for any accounting purposes.
How the Transaction was assigned its category.
See the categorization guide for more details.
ai, rules, similarity, transfer_between_accounts, uncategorized, user The ID of the Journal Entry that the Transaction's Line Entry is associated with.
The transaction's Journal Entry. Included in expanded responses.
The ID of the financial account ledger associated with the Transaction.
The transaction's ledger. Included in expanded responses.
The ID of the financial account ledger associated with the Transaction.
The transaction's Line Entry. Included in expanded responses.
A list of IDs of all the Line Entries
objects in the journal entry with the opposite debit_credit status. For
example if the Transaction's line entry is a debit this opposing line entries
will be credit line entries.
The transaction's opposing Line Entry. Included in expanded responses.
A list of all the Tags associated with the Transaction, if any. Note that Tags are not transitive and the tags on a Transaction can be different than those on its line entry or entires.
The ID of the Transfer
The transaction's ledger. Included in expanded responses.