Add new file in existing object using REST API

You can execute a POST to M-Files Web Service: Object files, including the new file content in the body as a stream.  The object must be checked out already and must be able to have another file added (e.g. by having the "single file document" property set to false).

That object is checked out and I just delete all files and need to update new files.
Files are uploaded in temp location.
When I am using UploadID and other details then getting this unnamed value

That approach is not supported.  As the documentation I linked to shows; you should push the file to the other endpoint instead.

That approach is not supported.  As the documentation I linked to shows; you should push the file to the other endpoint instead.

Need to upload local file using this API

So I upload file using this in Postman

and now I need to use this response info to this API

So I call this API with the upload info


and result is Unnamed.

I this process is right?
or something wrong I did?

No, this process is not right.  You should upload the file as raw *directly* to:

{{url}}REST/objects/{checkedOutObjectVersion.ObjVer.Type}/{checkedOutObjectVersion.ObjVer.ID}/{checkedOutObjectVersion.ObjVer.Version}/files

No temporary upload file.

Still Unnamed

Ahh, you are correct.

Have you seen the source to the sample library, as this does it: https://github.com/M-Files/Libraries.MFWSClient/blob/0f068c58d88219cd51c9cd9535ae1998888715b5/MFaaP.MFWSClient/MFWSVaultObjectFileOperations.cs#L479 

I just checking the code base, here 1st upload the local file to temp location in M-Files,

Then pass that uploadInfo variable in API
"/REST/objects/{objectType}/{objectId}/{versionString}/files/upload

in updateInfo variable
below data is stored

=================================

So in my postman call, Same URL, Same Title, Extension & Size to get the uploadInfo


Then using that info to File Upload as like as line 507 in the code base you shared.


What is the wrong I am doing?

Unfortunately I can't test this out for you right now.  By eye it looks like the sample code provides an array of UploadInfo instances and you provide just one, but that may not be the sole issue.

Yea, File count should be based on user, it can be one or multiple.
I tried multiple also.

I have to be clear: the endpoint being used by that is undocumented.  The official way is as I said earlier, then you would modify the file title.

However I did just check the REST API source code and at a minimum the final request body accepts a list of UploadInfo instances:

Which value is null in here ?

You don't seem to have an upload ID, at a minimum, if you've uploaded these already...?