> ## 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. # Create Re-upload Intent > Phase 1 of a re-upload: mint a NEW version of an existing file. Identical to a first-version upload intent from the client's perspective — declare the new bytes (name, MIME type, exact byte size) and receive a short-lived signed `uploadUrl` pinned to the declared content type and byte size. To complete the re-upload: 1. `PUT` the raw bytes to `uploadUrl` with the two signed headers (`Content-Type: ` and `x-goog-content-length-range: ,`). Bytes go straight to cloud storage — never through this API. 2. `POST /files/{fileId}/finalize` with the returned `versionId` — the SAME finalize endpoint first uploads use. Finalize flips the new version `ready` and repoints the file at it, so the new bytes silently become current. The file keeps its id, placements, categories, and full history. Because a re-upload changes an existing file, it is gated by `company.file:update` — not `company.file:create`. **Required permission:** `company.file:update` ## OpenAPI ````yaml /openapi/generated-external-api.yaml post /api/v1/companies/{companyId}/files/{fileId}/versions 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: post: tags: - Company Files summary: Create Re-upload Intent description: > Phase 1 of a re-upload: mint a NEW version of an existing file. Identical to a first-version upload intent from the client's perspective — declare the new bytes (name, MIME type, exact byte size) and receive a short-lived signed `uploadUrl` pinned to the declared content type and byte size. To complete the re-upload: 1. `PUT` the raw bytes to `uploadUrl` with the two signed headers (`Content-Type: ` and `x-goog-content-length-range: ,`). Bytes go straight to cloud storage — never through this API. 2. `POST /files/{fileId}/finalize` with the returned `versionId` — the SAME finalize endpoint first uploads use. Finalize flips the new version `ready` and repoints the file at it, so the new bytes silently become current. The file keeps its id, placements, categories, and full history. Because a re-upload changes an existing file, it is gated by `company.file:update` — not `company.file:create`. **Required permission:** `company.file:update` operationId: createCompanyFileVersionUploadIntent parameters: - $ref: '#/components/parameters/companyId' - $ref: '#/components/parameters/fileId' requestBody: required: true content: application/json: schema: type: object required: - fileName - contentType - byteSize properties: fileName: type: string description: File name for the new version (must be non-empty) contentType: type: string description: >- MIME type of the new version (e.g. `application/pdf`); must be an allowed type byteSize: type: integer description: >- Exact size of the new version in bytes (max 1073741824 = 1 GiB) examples: reupload: summary: Re-upload a revised document value: fileName: loss-run-revised.pdf contentType: application/pdf byteSize: 118220 responses: '201': description: >- Re-upload intent created — PUT the bytes to `uploadUrl`, then finalize content: application/json: schema: type: object properties: fileId: type: string format: uuid description: Id of the file (unchanged) versionId: type: string format: uuid description: Id of the new pending version — pass it to finalize uploadUrl: type: string description: >- Short-lived signed URL to PUT the new version's bytes to (expires in 15 minutes) examples: success: summary: Re-upload intent value: fileId: 550e8400-e29b-41d4-a716-446655440020 versionId: 550e8400-e29b-41d4-a716-446655440022 uploadUrl: >- https://storage.googleapis.com/bucket/companies/.../files/...?X-Goog-Expires=900&X-Goog-Signature=... '400': description: Bad Request — Validation error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: contentTypeNotAllowed: summary: Disallowed MIME type value: error: code: BadRequest message: 'Content type not allowed: application/x-msdownload' fileTooLarge: summary: Declared size over the cap value: error: code: BadRequest message: File exceeds the maximum upload size of 1073741824 bytes '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': description: File not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: notFound: summary: File does not exist value: error: code: NotFound message: 'File not found: 550e8400-e29b-41d4-a716-446655440020' '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 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 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. 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. ````