Search object with the ObjectGUID

VaultObjectOperations has GetObjIDByGUID method.

Thank you for your answer. 

OK, it's good for COM-API. Do you have the same function for REST APi ?

I just checked and there's no documented REST API endpoint that can accept a GUID, unfortunately.

Can I ask about the wider process here?

Bad news.

We want to add a M-Files existing document to our database. We need a simple process to do that without to add a new unique identifier property to the document.

Have you a proposition?

But why do you only have a Web link?  Can you describe more about the wider process?

We have a application that sends a document to M-Files. In order to modify, delete, update, show and download this file from the application we store the "Vault Guid", the "object Type" and the "object ID". Is doing so correct?

Now we imagine linking an existing document in M-Files within our application but we need in this case the Vault GUID, the object type and the object ID. But the end-user cannot get those informations from the user interface of M-Files web. How can we link our database to an existing document?

Best regards

It sounds like you have the object ID - the internal, numeric ID - as well.  This is typically the easiest thing to use to find an object.  You can use this with the REST API to retrieve the object data, and from this object data you can get the object GUID should you need to build a link.

Exist a method in the REST API to generate Shared Links (https://developer.m-files.com/APIs/REST-API/Reference/resources/sharedlinks/). With the data you provide, you could generate the link without many issues from your backend.

Exist a method in the REST API to generate Shared Links (https://developer.m-files.com/APIs/REST-API/Reference/resources/sharedlinks/). With the data you provide, you could generate the link without many issues from your backend.