# Upload file content Uploads file content for an existing upload session. Upload Process: - Upload content reliably with automatic error handling - System tracks progress automatically - Optional content integrity validation via checksum - Processes file when upload is complete - Creates content record upon completion Upload Flow: 1. Upload content using multipart/form-data 2. System processes content reliably on server 3. When upload is complete, assembles into complete file 4. Stores complete file in secure storage 5. Creates content record in database 6. Cleans up temporary files Error Handling: - Invalid content is rejected with detailed error messages - Failed processing triggers automatic cleanup - Session expiration prevents orphaned files Endpoint: POST /content-upload-sessions/{sessionId}/chunks Version: 1.0.0 Security: bearerAuth ## Path parameters: - `sessionId` (string, required) Upload session ID Example: "123e4567-e89b-12d3-a456-426614174000" ## Request fields (multipart/form-data): - `chunk` (string, required) Binary content data (max 900KB) - `chunkNumber` (integer, required) Content sequence number (1-based) Example: 1 - `checksum` (string) Optional SHA-256 checksum for integrity verification Example: "a1b2c3d4e5f6789..." ## Response 200 fields (application/json): - `sessionId` (string, required) Upload session ID Example: "123e4567-e89b-12d3-a456-426614174000" - `chunkNumber` (number, required) The chunk number that was uploaded Example: 45 - `uploadedChunks` (number, required) Total number of chunks uploaded so far Example: 45 - `totalChunks` (number, required) Total number of chunks for this file Example: 100 - `status` (string, required) Current status of the upload session Example: "uploading" - `isComplete` (boolean, required) Whether all chunks have been uploaded - `contentId` (string) Content ID when upload is completed Example: "987e6543-e21b-43d2-b654-321098765432" ## Response 400 fields ## Response 401 fields ## Response 403 fields ## Response 404 fields ## Response 413 fields