Remove Region
Changed onRemove a destination from the tracker.
A soft delete (active=False), not a row delete: the region carries immutable published snapshots we must not lose, and OSM/geo identity we'd otherwise have to rebuild if a reader re-requests the same place. Flipping active is enough to remove it everywhere that matters — the public map index, its public report page, and the weekly scan all filter on active — while leaving the history intact and the removal reversible.
Idempotent: removing an already-removed region succeeds without change, so a double click or a stale admin table can't 404 on a region that is, in fact, gone.
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/admin/source-tracker/regions/{slug}
- Auth: none declared
Path parameters
Response
Successful Response
Changes
- info
added the optional property
//to the response with the status - info
added the optional property
//to the response with the status
- info