> ## Documentation Index > Fetch the complete documentation index at: https://docs.go.aiinsurance.io/llms.txt > Use this file to discover all available pages before exploring further. # 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` ## OpenAPI ````yaml /openapi/generated-external-api.yaml post /api/v1/companies/{companyId}/files/{fileId}/versions/{versionId}/restore openapi: 3.0.3 info: title: AI Insurance External API description: External API for AI Insurance platform version: 1.0.0 contact: email: support@aiinsurance.io servers: - url: https://go.aiinsurance.io description: Production security: - ApiKeyAuth: [] paths: /api/v1/companies/{companyId}/files/{fileId}/versions/{versionId}/restore: post: tags: - Company Files summary: Restore File Version description: > 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` operationId: restoreCompanyFileVersion parameters: - $ref: '#/components/parameters/companyId' - $ref: '#/components/parameters/fileId' - $ref: '#/components/parameters/versionId' responses: '200': description: Version restored — it is now the file's current version content: application/json: schema: type: object properties: fileId: type: string format: uuid description: Id of the file (unchanged) currentVersionId: type: string format: uuid description: >- Id of the version that is now current (the restored version) examples: success: summary: Version restored value: fileId: 550e8400-e29b-41d4-a716-446655440020 currentVersionId: 550e8400-e29b-41d4-a716-446655440021 '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': description: File or version not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: fileNotFound: summary: File does not exist value: error: code: NotFound message: 'File not found: 550e8400-e29b-41d4-a716-446655440020' versionNotFound: summary: Version does not exist for this file value: error: code: NotFound message: 'Version not found: 550e8400-e29b-41d4-a716-446655440021' '409': description: Version cannot be restored content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: notReady: summary: Version is not finalized value: error: code: Conflict message: >- Version is not ready to restore: 550e8400-e29b-41d4-a716-446655440021 alreadyCurrent: summary: Version is already current value: error: code: Conflict message: >- Version is already current: 550e8400-e29b-41d4-a716-446655440021 '500': $ref: '#/components/responses/InternalServerError' components: parameters: companyId: name: companyId in: path required: true schema: type: string format: uuid description: Company identifier fileId: name: fileId in: path required: true schema: type: string format: uuid description: File identifier versionId: name: versionId in: path required: true schema: type: string format: uuid description: File version identifier responses: Unauthorized: description: Unauthorized - Invalid or missing API key content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: missingApiKey: summary: Missing API key value: error: code: AuthenticationError message: API key authentication required userMessages: - API key authentication required invalidApiKey: summary: >- Invalid API key (e.g. unknown key, or a Bearer token used instead of an API key) value: error: code: AuthenticationError message: Invalid API key userMessages: - Invalid API key Forbidden: description: Forbidden - Insufficient permissions content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: insufficientPermissions: summary: Insufficient permissions value: error: code: AuthorizationError message: User is not authorized to perform the requested action userMessages: - User is not authorized to perform the requested action companyMismatch: summary: A valid API key naming another company in the URL value: error: code: AuthorizationError message: API key is not scoped to the requested company userMessages: - API key is not scoped to the requested company InternalServerError: description: Internal Server Error - Unexpected error occurred content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: internalError: summary: Unexpected server error value: error: code: UncaughtActionError message: Uncaught error occurred in userMessages: - An unexpected error occurred. Please try again later. schemas: ErrorResponse: type: object description: Standard error response for all external API endpoints required: - error properties: error: type: object required: - code - message properties: code: type: string description: Machine-readable error code example: VALIDATION_ERROR message: type: string description: Human-readable error message example: 'submissionId: Required field is missing' userMessages: type: array description: >- Clean, verbatim-displayable messages — one entry per failure, free of error-code tags, field paths, and internal noise. Suitable for showing to end users as-is. items: type: string example: - Exposures of type 'company' require an address details: type: array description: Additional details for validation errors (field-level errors) items: type: object properties: field: type: string description: The field that caused the error example: submissionId message: type: string description: Description of the field error example: Required field is missing securitySchemes: ApiKeyAuth: type: apiKey in: header name: Authorization description: >- 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. ````