Zach,  If your intention is to access objects using a user defined key then you may consider using the namespace interface.  It allows you to store objects using filenames such as picture1.jpg, etc.  The namespace interface provides file system semantics that you may be looking for, but it also forces the developer to manage the keyspace for objects.  In other words, as a developer you wouldn't want to create an excessive number of objects in the same directory.  The object interface allows developers to store objects, but Atmos defines the key.  In this case the key in the key space is the object ID.  There's less management of the objects from the developer perspective, but also less control over the object or key name.   Many applications will choose to persist the object ID in their own database and map that internally to filenames, etc.  This is the recommended method if possible.  Are you using one of our Atmos wrappers?  Can you describe your application a little more?  Happy to answer other questions or speak on the phone if necessary.   Raj
I'm struggling to understand the use cases around using "ObjectID" method. I don't see a way to present the filename of the object, and so retrieving the file I need is difficult. Suppose I upload a file “picture1.jpg” and also tag it with “pictures”, and then upload another file named “picture2.jpg” and tag it with “pictures”. I can perform a metadata Tag search for “pictures” but I will be presented with two object IDs, and no way to actually know which Object ID is the file I want. Is there a way to identify a specific file?  It would be great to get an answer on how to retrieve a specific file if there are multiple objects attached to the same tag(s). Also, to hear some hear some possible use cases around this method.  I'm also curious, are there any noticable differences in performance when using the ObjectID method over the Namespace method?  Many thanks, Zach
Questions around REST API ObjectID method / use cases.