Update Viz
PATCH/v1/viz/:viz_id
Update viz metadata.
Slug handling mirrors the create path: a structurally-invalid slug
(forbidden word / bad charset) is a hard 409 up front, and a collision
with an existing viz on the same account surfaces as a clean 409 via the
VizSlugConflictError raised by the SQL layer's IntegrityError guard.
Previously a combined {name, slug} PATCH onto a taken slug let the
bare IntegrityError propagate → opaque 500 (ticket
viz-create-name-slug-combined-patch-500). Unlike create we do NOT
auto-suffix on update — the caller asked for a specific slug, so a
collision is a 409, never a silent rename.
Request
Responses
- 200
- 404
- 422
Successful Response
Not found
Validation Error