Restore the theme's draft content to a past published version
Applies one published version back to the theme, for a client that has no local checkout to stage it in. The git_archive_url operation is the equivalent for one that does.
Publishes as it writes: every record goes through the theme’s own write seam, which publishes it. Publishing is per record and there is no whole-theme publish, so a restore that only touched drafts would leave the caller publishing every template by hand. For an active theme this therefore goes live.
It remains undoable: the version being left behind is still in the history this restored from.
The version is read as a single archive rather than file by file, and applied in one transaction: a tree that cannot be written leaves the theme as it was rather than half-restored.
Files the target version does not contain are removed, which is what makes this a restore rather than a merge — a template added after that version would otherwise survive into a tree that never had it.
Undoing a restore is another restore: the version you were on is still in the history you restored from.
Authorizations
Bearer token authentication
Path Parameters
Application theme ID
Body
Commit SHA to restore, as returned by the git_versions operation. Accepts an abbreviated (7+ character) SHA.