Get Inventory Reconciliation Adjustment Journal
GET/api/ledger/reconciliation/inventory/adjustment/journal
Where a posted inventory reconciliation adjustment landed in SKU's ledger — so a client can deep-link the user to the journal entry the adjustment created. The adjustment posts asynchronously, so immediately after posting this returns pending: true with null ids; poll it with the returned adjustment_id until pending is false, then use journal_entry_id to open the journal.
Authentication: Requires Bearer token.
Response fields: pending (true until the journal exists), journal_entry_id (the created journal entry's id, null while pending), reference (the journal's reference, e.g. INV-RECON-ADJ-1), status (the journal's lifecycle state, e.g. draft or posted), deletable (true while the journal has not yet synced to the provider — so the adjustment can be reversed and discarded cleanly).
Request
Responses
- 200
- 401
- 403
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.