Restore File Version
Restore a previous version of a file by making it current again. This repoints the file at the named version — pure metadata, so no bytes move, nothing is deleted, and the previously-current version stays in the file’s history. It is the rollback counterpart to a re-upload: a consumer that pushed a wrong new version rolls back by restoring the version it wants current.
Only a finalized (ready) version can be restored. Restoring a version
that is still pending (or otherwise not ready) returns 409, as does
restoring the version that is already current. An unknown versionId, or a
version that belongs to a different file, returns 404.
After a restore, the download URL serves the restored version’s bytes and the file keeps its id, placements, categories, and full history.
Because a restore changes an existing file, it is gated by
company.file:update — the same permission as re-upload.
Required permission: company.file:update
Authorizations
API key authentication. Send your raw API key as the Authorization header value with NO scheme prefix — Authorization: YOUR-API-KEY. Do NOT prefix it with Bearer or ApiKey, and do not use an X-API-Key header; those are not accepted.
Path Parameters
Company identifier
File identifier
File version identifier
