Update an accounting entry
Code an entry: its memo, dimensions, custom fields and, for transaction entries, how it’s split into lines.
Authorizations
User API key authentication. Create a key under Settings → API keys in the Slash dashboard (https://app.slash.com/global-settings/api-keys) and send the x-legal-entity header naming the legal entity to act on with every request. Keys scoped to a legal entity are rejected with 403 user_api_key_required.
Headers
Body
How an entry is coded. Omitted fields are kept and null clears a clearable field. Nothing here changes the entry's status; use the status actions for that.
Coding applied across the entry, by dimension key. On a transaction entry account is set on every editable line and every other dimension on every line. On a bill entry these are the bill-level values: vendor and subsidiary land on the accounts-payable line, account is the expense account of every line, and any dimension named in lineItemLevelDimensions must be coded per line instead. A value id sets the dimension, null clears it, and an omitted key leaves it alone.
On a transaction entry, the complete set of editable lines after the update: lines with an id are changed in place, lines without one are new splits, and editable lines whose ids are left out are removed. Their amounts must total the transaction amount. fixed lines may be listed by id to recode them. On a bill entry, lines mirror the bill's line items, so every line needs an id and only its coding can change.
1 - 100 elementsResponse
The entry as coded.
The accounting record for one settled transaction (or group of related transactions) or one bill. An entry is created automatically when its source settles, coded with dimensions on its line items, and then synced to the connected platform. status tracks that lifecycle.
What the entry represents on the platform. expense_card and expense_card_refund come from card transactions; bank_transfer, bank_deposit, and expense from account transactions; journal_entry from transactions posted as journals; bill is the accounts-payable bill and bill_payment the transaction that settles one. unknown entries have not yet been classified.
unknown, expense, bank_transfer, bank_deposit, journal_entry, expense_card, expense_card_refund, bill_payment, bill in_review until a user or rule marks it ready; ready_to_sync when coding is complete; pending_sync and syncing while a sync is queued or in flight; synced once the platform holds it; failed when the platform rejected it (see lastSyncError); archived when excluded from the books.
in_review, ready_to_sync, pending_sync, syncing, synced, archived, failed