V1 / Shaders
Update a shader
Editing source or the manifest re-runs the full vetting pipeline and produces a new content hash — an existing approval is never inherited by code that was not vetted. A rejected edit returns 422 and leaves the stored shader untouched.
V1 / Shaders
Update a shader
Editing source or the manifest re-runs the full vetting pipeline and produces a new content hash — an existing approval is never inherited by code that was not vetted. A rejected edit returns 422 and leaves the stored shader untouched.
PUT
/api/v1/shaders/:idResponses
200
JSON { doc, report }
404
No such shader
422
Rejected by vetting; the stored shader is unchanged
Request
curl -X PUT "http://localhost:3000/api/v1/shaders/:id" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-d '{}'Response
// JSON { doc, report }
{
"success": true,
"data": { ... }
}