Report a landmark as wrong for turn-by-turn narration

POST 
/v2/landmarks/:slug/report

Crowdsourced, anonymous — no API key, no admin review queue, same posture as POST /v2/route/incidents. Reports for the same landmark reinforce (increment report_count) rather than duplicate; there's no expiry, since a wrong landmark match is a persistent data problem, not a transient event. Once a landmark accumulates enough corroborated reports, it's automatically excluded from narration candidate selection (instruction_landmark/landmark_confidence/alternate_landmarks on POST /v2/route) until reviewed — general landmark search, geocoding, and POI density are unaffected.

Request

Responses

201

Report recorded

400

Missing slug, invalid reason, or note too long

404

No landmark with that slug

429

Rate limit exceeded

Response Headers

X-RateLimit-Limit

Maximum requests allowed in the window

X-RateLimit-Remaining

Requests remaining in current window

Retry-After

Seconds until the rate limit resets