How to use /v2/nodes/{id}/versions

If you are a new programmer it is kinda hard to understand however the trick is to understand POST in a webserver

POST is a name/ value pair operation so, in this case, we create a fake "body","name","filename" etc so when you submit the request the whole payload goes in as name/value pairs including the file that you post in that call. The HTML body is not the "body" OpenText talks about.

in this reply if I am not mistaken I have shown a Postman payload as well as some ways to do this once you understand it in Postman convert it into a language of your choice

https://forums.opentext.com/forums/developer/discussion/312086/does-create-document-in-v2-nodes-api-support-multipart-form-data#latest

Uploading the first and the subsequent version is pretty much the same except for the rest api involved.

Another trick we all use is the SMARTUI of OpenText, which is a client that converses through the server using REST so you can observe the payload it would be similar to what your Postman experiment tells you

OT allows you to send the file only to the web server or application server of OTCS. They don't support picking up a file in a CIFS/SMB share or encoding it with base64.

another recent example with POSTMAN

https://support.opentext.com/community?id=community_question&sys_id=b7ad2bde97c9c21034127e400153af0f&view_source=searchResult

I don't know to say yes or no. if you cannot use POSTMAN try it on a personal machine or use the network tab of a smartui upload and trace the payload

the sender is using multipart/form data and not JSO for the request that is paramaount

I am seeing this in my network tools/fiidler

POST /otcs/cs.exe/api/v1/nodes HTTP/1.1
Host: myserver:8080
otdsticket: OTDSSSOAahBQlNza0xkQ3Bycm1sbHlyOUx6LVUzUE5mV0NmeGdBTTlXWlhjVExzX3ZKRkNrZm5BUmRBWGk2MERZNHlrNXBIYWxuY2lyajVTXy05T3pLa3ZiZzdJblJsdXNweFpWNi1hUnE1c2Uwak9EakU3UmtfUWg1ZjdZekNkVjRtQmZOUHl6Y0ZocGkzLTJROTg4cHE1dURvWnpFc09NU1daUmtKLWVSWWJkWjlBMHRnWWlzNkRYWTBPM1o3UXRzcmhzelpiZUN6WkdmazBReDVOWWxBdlFYMVU2ZFRHaEhQVUJQYjQ4eXhzNkE1VlhfQ2J0Zmp1cF9fZll4U3N2M1BFZHRXMmdQYlZfX2FqWVJxMXNZQ0ZldVRBWkpGamtSMXNzNlJjV2xKMm90d0F0Tk1aN3FBQzNtU1hUa3NPdHR1WEpPNTUtQ1BRYS1zbVpUdThyemFuVFVhSFFUb2RUWFBwUmNwRV83Zjllcl95Y0dUV2tad2szQ05UZzZrZXFrT1doZ0w4eEw5RDdMdHluc0ZGU09HZWtoTm93LVMzWXVyemdzQWRFU2o5ZmMqAE4ASgAUPYQ13uu1FoVqEjENgXatog6tg24AEGj2sghHvv6SqFhrQiABNSEAIFStWWYbeg-32lSq44Pjs2Jwchqubr8CW7Z-x7fWjmiLAAA*
Content-Length: 523
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW

------WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="type"

144
------WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="parent_id"

2000
------WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="name"

Filename for CS
------WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="file"; filename="///mycifsshare/c$/temp/AIMSuiteRESTlog4net.log"
Content-Type: <Content-Type header here>

(data)
------WebKitFormBoundary7MA4YWxkTrZu0gW--

Your payload looks different do you want a simple html file that does this?

adding a version is very similar to a creating a node and a version for the first time, sanitized code ,The form data element called body is where you put anything extra like a description

POST /otcs/cs.exe/api/v2/nodes/209636/versions HTTP/1.1

Host: myserver:8080

otdsticket: *OTDSSSO*AaxBQlRtZQ4Sb2n0ib1Bknpzq7533YsnD83SwAA

Content-Length: 419

Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW


------WebKitFormBoundary7MA4YWxkTrZu0gW

Content-Disposition: form-data; name="body"


{"external_modify_date":"2024-10-18T14:57:47.990Z"}

------WebKitFormBoundary7MA4YWxkTrZu0gW

Content-Disposition: form-data; name="file"; filename="/C:/Users/appuq/OneDrive/Desktop/Screenshots.docx"

Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document


(data)

------WebKitFormBoundary7MA4YWxkTrZu0gW--

you can see I am using OTDSTicket OTDSTicket gets exchanged internally for an OTCSticket.If you do rapid-fire succession against OTCS clusters unless the OTCS servers are set correctly the OTCS server will sometimes balk at an OTCSticket from another server. By trial and error, I have found OTDStickets having much more luck :)

file=<full pathname>; file_content_type=<mime type>;file_filename=<filename>

Should I define those as an "associative array" as you have done with external_modified_date?

You are on your own there I doubt from a JSON string how a server can know it is a file, in actual HTTP protocol to send a file either you need to stream it or send a file, I think we are sending the file by making it into a multi part

You might try to get an official answer from OT on that and most likely they will say to use their professional services but if you try to send a file like that

{

    "file": "/C:/appu.docx", (I tried various permutations/combinations:))

    "file_content_type": "application/vnd.openxmlformats-officedocument.wordprocessingml.document",

    "file_filename": "appu"

}

{

    "error": "Error: File could not be found within the upload directory.",

    "request_id": "f93aa620-1617-4007-b03e-f14244b26bda"

}

I am a content server programmer, so I could debug it, but I have no time. I guess that the CS server has an upload directory set, and if you put the file in the server it will change to something like this. A long time ago, OT would allow files to be accessible on the server. It was probably removed as it could be a security hazard, so maybe the low-level code may be geared to look for a POST-ed file.

{

    "error": "An illegal attempt was made to upload a document",

    "request_id": "c4f29be5-6f9a-4ffe-bfb6-50172d5188e5"

}

BTW code along the lines posted above is what I used in an IBM Tivoli integration not long ago :)