Skip to main content
GET
Preview Application Rollback
Returns which environment variables would change if you rolled the application back to this release and restored its variables. Only the variable names and the kind of change come back, never the values. Nothing is changed. Rolling back does not restore variables unless you ask it to. Check this preview first, then send the rollback request with restore_environment: true if the changes are the ones you want.
string
required
The ID of the application. If the application belongs to a workspace, pass its ID in the workspace_id query parameter.
string
required
The ID of the release you would roll back to, as returned by the release list.
string
If the application belongs to a workspace, the workspace’s ID.
Each change is compared with the current variables of the application, including the ones saved but not yet applied by a restart. Those are the variables a rollback overwrites:
  • added: the release has the variable, and the current variables do not.
  • removed: the current variables have the variable, and the release does not. A variable created after the release and not yet applied by a restart appears as removed.
  • modified: both have the variable, with different values.
The list is sorted by key. It is empty when the release has no saved variables, or when restoring them would change nothing. Requires the apps:envs scope when called with an API key. For a workspace member, it requires the apps:envs permission.

Response

object
The variable changes a rollback would make.

Error Responses

string
Possible error codes:
  • UNAUTHORIZED: User is not authenticated or lacks permissions.
  • APP_NOT_FOUND: The application does not exist, or it is not owned by this account or workspace (404).
  • RELEASE_NOT_FOUND: The release does not exist, or it belongs to another application (404).
  • PLAN_DOES_NOT_SUPPORT_ROLLBACK: Your plan does not include rolling back to earlier releases (403). Rollback starts on Pro.
  • API_KEY_SCOPE_DENIED: The API key does not have the apps:envs scope (403).
string
A descriptive message providing additional details about the error.
A release keeps the variables the application was started with. Releases created before this feature launched have none saved, so their preview is always empty.