Agent Versioning - Revisions
Restore a revision
Republish an older revision as a new revision at the head of this branch. Restore does not overwrite history; the older revision keeps its ID, and a new revision is committed on top.
The response mirrors POST /agent/{id}/branches/{branchId}/draft/publish: 200 committed if the scan is synchronous, 202 scanning if deferred. Only one publish or restore can be in flight per branch at a time.
post/agent/{id}/branches/{branchId}/revisions/{revisionId}/restore
Path parameters
idstring required
The agent ID.
branchIdstring required
The branch ID.
revisionIdstring required
The revision ID. Equal to the v1 versionId for revisions that were migrated from the v1 model.
Response
Restored synchronously.
Example response
{
"status": true
}