Box account with our own Box connected app
Hi, Today while creating the Box account, SnapLogic internally uses a connected app in Box (client_id=4y9mpks2hql3xchpudijkct1vfhwwklx), it is not possible to override this with our own connected app. Due to this at the Box side all the API calls are registered against “Snaplogic app” connected app. There is no way to track which project in SnapLogic is actually using the APIs. In our case we have many projects uses Box, each have their own quota of Box usage, since SnapLogic is using same connected app at the Box side we are not able to govern the Box usage accurately. Is there a way or implementation plan in progress to allow feed in out own client_id for Box account? Regards, SripathiBox Snap - Read file/folder properties
Hi, Current Box snaps does not allow to read file/folder properties like owner, created, udpated dates etc. Also when the folder is empty there is no way to get the folder path using folder id. Are there any enhancements coming for the Box snap pack which will address these gaps? Regards, Sripathi
Other BOX APIs - BOX Account
We have the BOX snap pack, and use many of the pre-built BOX snaps for writing files, etc. with an associated BOX account for our system. BOX has many other APIs that don’t have pre-built snaps though, such as administrative APIs for managing domain whitelists, etc. I can probably just use the REST API snaps for the other types of APIs, but need to be able to leverage the same BOX account used by the BOX snaps. Is there a way to somehow leverage the BOX account with the REST API?