Is there any way to update the content of a document through the API? Im not talking about the information about the document, which can be updated with a PUT call to /projects/{project_id}/documents. Im talking about the actual binary content of the document. The only way I can see to update the content of a document programmatically is by uploading a new copy of the document and deleting the existing one. en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spiraplan/issues-questions/3184.aspxthreadId=3184Andrew McIntyre (andrew.mcintyre@tracsis.com) Is there any way to update the content of a document through the API? Im not talking about the information about the document, which can be updated with a PUT call to /projects/{project_id}/documents. Im talking about the actual binary content of the document. The only way I can see to update the content of a document programmatically is by uploading a new copy of the document and deleting the existing one. Tue, 31 Mar 2026 23:01:56 -04002026-04-13T10:34:46-04:00/Support/Forum/spiraplan/issues-questions/3184.aspxmessageId=7590Victoria D (nino.diasamidze@inflectra.com) Hello, I think that it is not currently possible - there is no direct replace binary content call on an existing document record. If Spira receives a POST request with a DocumentId that already exists, it will automatically append the new BinaryData as a brand-new version (e.g., v2.0) of that existing document, rather than creating a new record. So, yes - because Spira uses built-in version control, the correct way to update the content programmatically is to upload the new copy as a new version of the same document. Why this is the best practice: - It preserves Links: The DocumentId remains the same, so any existing artifacts linked to this document will now seamlessly point to the newly uploaded version. - History is being maintained: If you look at the document in the Spira UI, you will see the new binary file as the Current Version, but users can still go to the Versions tab to see the previous iterations. Hope that helps. Regards, Victoria - Wed, 01 Apr 2026 10:16:02 -04002026-04-01T10:16:02-04:00/Support/Forum/spiraplan/issues-questions/3184.aspx#reply7590messageId=7594Debbie Adams (Debbie219Adams@outlook.com) Hello! Most APIs only allow updating document metadata with a PUT call, not the binary content itself. To change the actual file, you typically need to upload a new version and then delete or archive the old one. Some systems expose this as a replace or upload new version endpoint, but under the hood its still a fresh upload-so re‑uploading and removing the old copy is the standard approach unless the API supports explicit versioning. Mon, 13 Apr 2026 10:34:46 -04002026-04-14T08:28:20-04:00/Support/Forum/spiraplan/issues-questions/3184.aspx#reply7594