Vendor and work-order list APIs: an address naming a building the company does not hold is refused

Row ui-s-d-part2, part 43. Staff login, Wei Slope Mirror (TEST). Stage, this branch. The raw API response, as the browser shows it.

1 Oct 2026 · branch uisd-p2-one-refusal-pair · captured against propflow-stage · at a9826ef46b0+local

Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.

1 · 1 · Control — the company named, the list answers

The company named, no building: the route answers with rows.

Asserted in the captured DOM — rows · nextCursor. A list response.

1 · Control — the company named, the list answers
Sections 2–4

2 · 2 · A building the company does not hold — refused, not the company's whole list

On main the unknown building was dropped and the route answered with the whole company's vendors. It now refuses, the same as its page.

Asserted in the captured DOM — needs_a_selection. The refusal body.

2 · A building the company does not hold — refused, not the company's whole list

3 · 2b · Control — work orders with the company named

The company named, no building: the work-order list answers.

Asserted in the captured DOM — rows. A list response.

2b · Control — work orders with the company named

4 · 3 · Work orders, the same address — refused, not the company's work orders

On main the work-order list answered the company's whole list here too. It now gives the building refusal from the shared door.

Asserted in the captured DOM — org_not_answerable. The building refusal body.

3 · Work orders, the same address — refused, not the company's work orders
PropFlow Docs