Find the target deploy: GET https://api.render.com/v1/services/{serviceId}/deploys (filter by status / finishedBefore etc., cursor+limit pagination) and note its deploy id (https://api-docs.render.com/reference/list-deploys).
POST https://api.render.com/v1/services/{serviceId}/rollback with body {"deployId": "<deploy to restore>"}. 201 = rollback created (https://api-docs.render.com/reference/rollback-deploy).
Known gotchas
Rolling back does NOT disable autodeploys — the next git push can immediately re-deploy the code you just reverted. Disable autodeploy via the Update service endpoint or Dashboard first if needed (https://api-docs.render.com/reference/rollback-deploy).
403 = your key lacks permission on that service; 404 = service or deploy not found (https://api-docs.render.com/reference/rollback-deploy).
Give your agent this knowledge — and 18,200+ more routes
One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?