logs

Bulk Mark Reviewed

Changed on

Record one reviewer's verdict across many logs.

Upserts one review per (log, reviewer) and writes the log's review_status in the same transaction, honouring the sole-writer invariant: those four columns are only coherent together, and a bulk path that wrote review_status alone would be the fastest possible way to produce logs that read as reviewed with no verdict behind them.

There is deliberately no bulk un-review. The design shows none, and removal stays in the detail panel.

post/api/v1/logs/bulk-mark-reviewed

Request

  • Base URL: https://api.getanana.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.getanana.com/api/v1/logs/bulk-mark-reviewed
  • Auth: none declared

Request body

subject'voice' | 'text' | 'email' | 'booking' required
idsstring[]
verdict'good' | 'par' | 'bad' required

Reviewer's coarse verdict on the whole call (V0.5).

The three values cover the spectrum without overclassifying: the agent nailed it, met the bar, or fell short. Annotations carry the signal — the verdict is a coarse summary only. See sync_review_to_findings.py for the uniform "verdict + 0 annotations → 0 findings" rule (intentional extension beyond the briefing's §9, which only guaranteed it for good/par; V0.5 extends it to bad so the sync function has one consistent rule).

outcomestring required

Response

Successful Response

updated_countinteger required
matched_countinteger
failed_idsstring[]

Changes

  • a9cebb28e243Revision changes
    • info

      added the new optional request property ////

  • 38818ad2a896Revision changes
    • info

      added the new opera_sync enum value to the request property //////