What is actually walking, the pending claims retailers have made against their book
The pending claims retailers have made against their book: one row per claim with the account, the line it names, the claim type, what the retailer wants, the line's current booked value and quantity, the source text it was read from, and when it was raised, with totals by type.
season_code is required; commitment_id and as_of narrow as elsewhere.
The money on each row is the brand's, not the retailer's: it is the line's current booked value, what is at stake if the claim is accepted, never a figure the retailer sent.
Only pending claims are counted. An approved signal has already been applied through the book's one writer, so counting it again would double the exposure, and an ignored one was judged not to be a change; both stay on file because the trail is the point. A claim naming no line is served and counted separately under unsized_claims rather than pooled into the money.
get_order_book_firmness says what can walk, classified from the term an account agreed to. This says which of it somebody has moved on. Recording or deciding a claim is not public.
Sold with Essentials+: without Tightly Connect the answer is 403 plan_excludes.
Scope: order_book:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/order-book/signals
- Auth: HTTP bearer
Query parameters
The season being read, e.g. SS27.
Narrow the book to one Commitment's scope.
Reconstruct the book as it stood at this instant (ISO-8601). Default is now.
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
Every pending claim with the account, the line it names, what the retailer wants, the line's current value and, where it has none, the reason it cannot be sized; plus totals that keep the sized money and the unsized claims apart.
Changes
No recorded changes to this operation across all 1 revision of this API.