Skip to main content
GET
List all Line Entries in a Journal Entry

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer , where is your auth token.

Headers

teal-instance-id
string
required

The Teal instance ID

Path Parameters

journal_entry_id
string
required

Journal entry ID

Query Parameters

expand
enum<string>[] | null

Comma-separated list of Line Entry expand paths.

Available options:
transaction,
ledger,
journal_entry,
opposing_ledger_ids,
payment_applications,
line_payment_applications,
accrual_source

Response

Successful Response

amount
number
required

The value of the line entry in decimal dollar cents.

Example:

"31282.27999999999883584678173065185546875"

debit_credit
enum<string>
required

Indicates if the amount is a credit or debit.

Available options:
debit,
credit
Example:

"credit"

ledger_id
string
required

The ID of the Line Entry's Ledger.

Example:

"7JRNsKwy2Lw66caxVU7WGC"

id
string | null
required

The unique ID of the object.

Example:

"XMDsKVuW4Wmi3LTW31Qw6E"

datetime
string<date-time>
required

The datetime the Line Entry was created in UTC time.

Example:

"2023-02-15T06:42:18Z"

editable
boolean
required

Indicates if the Line Entry can be manually added or removed from a Ledger, as dictated by the editable property on the Ledger.

Example:

true

journal_entry_id
string | null
required

The ID of the associated Journal Entry.

Example:

"C4ocnUQze8kDwQ3EczkZXn"

journal_entry_description
string
required

An arbitrary string on the object, useful for displaying to users.

Maximum string length: 512
Example:

"Payroll#230215"

categorization_status
enum<string>
required

Whether the associated Journal Entry is still awaiting an auto-categorization result: 'pending' (awaiting), 'delayed' (timed out, a late result may still resolve it), or 'completed' (resolved, or not auto-categorized). Both Line Entries of a Journal Entry share this value.

Available options:
pending,
delayed,
completed
Example:

"completed"

ledger_name
string
required

The name of the Line Entry's Ledger.

Example:

"Payroll Expense"

description
string | null

An arbitrary string on the object, useful for displaying to the user or for categorization.

Maximum string length: 4000
Example:

"Payroll#230215"

related_line_entry_id
string | null

If the Line Entry is identified as a transfer between accounts, the ID of the Line Entry in the opposing Ledger. Related guide: Auto-categorization

transaction_id
string | null

The ID of the associated Transaction, if one exists.

sort_order
integer | null

The position of the Line Entry within its Journal Entry, used to determine display order.

Example:

1

journal_entry
JournalEntry · object | null

Expandable. The associated Journal Entry object.

Example:
ledger
Ledger · object | null

Expandable. The associated Ledger object.

Example:
opposing_ledger_ids
string[] | null

Expandable. IDs of the ledgers on the other side(s) of the line entry with opposite debit/credit.

tags
Tag · object[] | null

A list of all the Tags associated with the Line Entry, if any.

transaction
Transaction · object | null

Expandable. The associated Transaction object, if one exists.

Example:
payment_applications
LineEntryPaymentApplication · object[] | null

Payments applied to an accrual source (bill/invoice) using the Line Entry.

line_payment_applications
LineEntryLinePaymentApplication · object[] | null

Payments applied to specific payroll lines of an accrual source using the Line Entry.

accrual_source
AccrualSource · object | null

The accrual source linked to a line entry, if one exists.