Swap (replace) the on-disk asset for an existing Upload

Replaces the physical bytes under an existing Upload record without regenerating embeddings or touching ingestion state. The Upload _id, filename, and file_url stay byte-identical so any published links continue to resolve. Existing embeddings, file_title, file_summary, and vaultHealthScore are preserved — to re-index the new content, call the Reprocess Content endpoint afterwards.

Two input modes (mutually exclusive):

• Multipart file field with the new asset bytes.
• JSON { url } body — server fetches the URL and writes it into place. SSRF guard mirrors /api/user/url.

Authorization mirrors the rename endpoint: the caller must own the upload, or hold files.edit on the upload’s institution.

PUT /api/user/upload/{fileId}/swap-asset

Swap (replace) the on-disk asset for an existing Upload

cURL

curl --request PUT \
  --url https://pria.praxislxp.com/api/user/upload/{fileId}/swap-asset \
  --header 'Content-Type: multipart/form-data' \
  --form file='@example-file' \
  --form updateOriginalName=false

200

{
  "success": true,
  "message": "<string>",
  "data": {}
}

Path Parameters

fileId · string · required

The Upload _id to swap the asset for

Pattern: ^[0-9a-fA-F]{24}$

Body

multipart/form-dataapplication/json

file · file

The replacement asset (max 500 MB)

updateOriginalName · boolean · default: false

When true, rewrite the displayed originalname to the uploaded file's name. The on-disk filename and file_url always stay stable.

Response

200

application/json

Asset swapped successfully. Embeddings are preserved.

success · boolean

Example:

true

message · string

data · object

Updated Upload document