Mark an accounting entry ready to sync
Approve an entry for syncing.
entry_not_ready listing what to fix.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
Response
The entry, now ready_to_sync.
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