Get Inventory Reconciliation Opening Breakdown
GET/api/ledger/reconciliation/inventory/opening-breakdown
The warehouse-first opening breakdown for reconciling inventory to the accounting provider. For each earmarked inventory control account, returns the provider general-ledger balance and its divergence from the SKU inventory value at the opening date, broken down into the individual warehouses that hold that account's stock. The provider balance and divergence are reported at the account level (a provider account has no warehouse dimension); the SKU side sums standard and Amazon FBA inventory per warehouse. Warehouses that currently hold no stock are still listed so an account's full warehouse footprint is visible. The opening date is the reconciliation baseline when one has been set, otherwise the configured inventory start date. Reads materialized/cached data only — no live provider call.
Authentication: Requires Bearer token.
Response fields: as_of_date (the effective opening date, null when no accounts are earmarked or no opening date is configured), from_baseline (whether as_of_date came from a set baseline rather than the inventory start date), accounts[] — each with nominal_code_id, code, name, provider_account_name, sku_value (sum of its warehouses), sku_quantity, provider_balance, divergence (provider_balance minus sku_value, null when no provider balance is available), point_as_of_date (the day the provider balance was measured), and warehouses[] (warehouse_id, warehouse_name, is_fba, sku_value, sku_quantity). Each account also carries unsynced_ledger — SKU ledger postings dated on/before the opening that haven't synced to the provider yet; adding it to divergence shows how much of the opening gap is just unsynced pre-baseline activity (self-resolving) versus a true gap. Each account also carries pending_ledger (unsynced activity dated on/before the opening that WILL sync) and excluded_ledger (activity that will never sync — the pre-baseline mismatch the baseline sets aside).
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.