RErender
Deploys

Roll back deploy

Changed on

Trigger a rollback to a previous deploy of the specified service.

Triggering a rollback with this endpoint does not disable autodeploys for the service. This means an autodeploy might restore changes you had intentionally rolled back.

You can toggle autodeploys for your service with the Update service endpoint or in the Render Dashboard.

post/services/{serviceId}/rollback

Request

  • Base URL
    https://api.render.com/v1
  • Auth
    HTTP bearer

Request body

deployIdstring required

The ID of the deploy to roll back to

Response

OK

idstring required
buildIdstring

The ID of the build this deploy shipped. Only present for deploys of a build from a Build Source.

status'created' | 'queued' | 'build_in_progress' | 'update_in_progress' | 'live' | 'deactivated' | 'build_failed' | 'update_failed' | 'canceled' | 'pre_deploy_in_progress' | 'pre_deploy_failed'
trigger'api' | 'blueprint_sync' | 'deploy_hook' | 'deployed_by_render' | 'manual' | 'other' | 'new_commit' | 'rollback' | 'service_resumed' | 'service_updated'
startedAtstring date-time
finishedAtstring date-time
createdAtstring date-time
updatedAtstring date-time

Changes

  • 6ac5d3d47362Revision changes
    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status