Queue Contract Price Re-reviews

Queue a re-review for one contract price row or for every contract price row not yet reviewed, with the write scope and a member role in the workspace.

Two routes queue re-reviews. POST /v1/money-found/rows/{leverId}/{key}/review queues one row. POST /v1/money-found/reviews/run queues every contract price row that no review covers yet. Both need the write scope and a key whose person is a member or above. The review runs in the background; the verdict appears in GET /v1/money-found/reviews and on the row's plausibility.review.

The review reads the invoice, the contract versions and the Contracts app documents again, and keeps a value only when its quote is found in the document. A review already pending or running is returned as is. A finished or failed one is queued again. The response is { "review": ... } in the shape of an entry of the reviews list. Errors: 400 when the lever is not a contract price lever or the key is not a contract price row, 403 for a missing scope or role, and 404 when the price check behind the row does not exist in the workspace.

curl -X POST "https://api.talonic.com/v1/money-found/rows/contract_price_underbilled/r_3f9a1c/review" \
  -H "Authorization: Bearer $TALONIC_API_KEY"

{ "review": { "id": "b3a0f6c4-7d1e-4a2b-9c58-0e6f1d2a3b47", "lever_id": "contract_price_underbilled", "row_key": "r_3f9a1c", "status": "pending", "verdict": null } }

The bulk route queues one review per group of identical contract price rows that no review covers yet, up to the configured bulk maximum. Rows that the invoice's own printed inputs already settle are not queued. A row keeps its key across recomputes, so a reviewed row is left alone until its billed price or contract price changes.

{ "queued": 12, "already": 31, "rows": 43 }