Which accounts reported which periods, and at what grain
Which accounts reported which weeks, and at what grain: the week axis once, and each account's reported weeks keyed against it with the units and variants it sent, its last reported week and its grain. weeks bounds the window.
Coverage is account against time, and a table of totals cannot show that an account stopped reporting four weeks ago.
A week an account did not report is ABSENT from its map, never a row with zero units. The source data does not agree on that point: one retailer lists every product every week and means its zeros, another lists only movement, so filling the gaps would decide the argument wrongly for one of them, and a reader seeing "0 units" could not tell a dead week from a week nobody sent. Inside a reported week units can still be null, because a stock-only week has no sales figure.
Derived rows, the brand's own curve scaled by an account's share, are excluded: a coverage grid counting them would claim an account sent weeks nobody sent.
Sold with Essentials+: without Tightly Connect the answer is 403 plan_excludes.
Scope: sell_out:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/sell-out/coverage
- Auth: HTTP bearer
Query parameters
How many weeks of axis to return. Clamped to 1 to 52.
Optional tenant-local book. Restricts reported variants to its canonical current cohort (future boxed books use their declared window). The response roster contains reported-activity accounts only, not expected reporters; expected_accounts is null. The organization-wide default is unchanged.
ISO date for commitment scope; requires commitment_id. Defaults to today.
Headers
The date train to answer on. One train exists today, 2026-11, the one this reference describes and the one every key is minted on, so the call answers on it with or without this header. Send it anyway, so a client built now names its train from the start.
Response
The week axis, one row per account with the weeks it reported and the grain it reports at, and the two counts a verdict is written from, how many accounts reported at all, and how many there are.
Changes
No recorded changes to this operation across all 1 revision of this API.