Hi Jason,  If the Atmos path is never exposed to users, I'd suggest you store all your files in one standard namespace. Using the namespace interface to upload files to Atmos ensures that the 'objname' attribute gets populated. Also, make sure you store the listable tags when you upload.  When you are looking up objects, use the Listable tags interface and not namespace. When you get the system metadata, you will get back the 'objname' value - using which you can construct the full path. Now, using that path call create shared URL API.  Hope that helps.  Aashish
Using the Java API, I'm trying to list all objects with a specific listable tag and return the full Namespace path of the object.  The problem I'm having is that listObjects returns the objectID.  I see no way to get the full path or the parent directory name given an objectID.  All namespace objects have SystemMetadata called "objname" that contains the name of the file or directory, but this isn't much use with out the path hierarchy.  I'm considering storing the path as UserMetadata, but if there is a standard way to do this, I don't want to reinvent the wheel.   Jason ThornbrughPrincipal Solutions EngineerGSC Demo Cloud 
listObjects with Namespace interface