Sign in
routes

Report Browser Route Run

Record "this route is wrong" against a served run (#1598).

The reason bucket triages; the reported candidate's seq into the run's durable events is what makes the report replayable — cheshire route-reports export turns it into an eval-fixture candidate without anyone reconstructing the geometry by hand, which is exactly the work the Seaport Village incident (#1589) needed done manually.

post/routes/{run_id}/report

Path parameters

run_idstring required

Request body

reason'not_what_i_asked' | 'wrong_distance' | 'wrong_place' | 'unsafe_or_impassable' | 'description_wrong' | 'other'
labelstring nullable
route_pathstring nullable
notestring nullable
localestring nullable
theme'light' | 'dark' nullable

Response

Successful Response

status'recorded' required
report_idstring required
run_idstring required
reason'not_what_i_asked' | 'wrong_distance' | 'wrong_place' | 'unsafe_or_impassable' | 'description_wrong' | 'other' required
candidate_labelstring nullable
first_reportboolean required

Changes

No recorded changes to this endpoint across all 1 revision of this API.