Using Box CLI to get Shared Link Report
Hi,
I am trying to figure out a way to use the CLI to generate the Shared Link report from the admin console. We have a requirement to automate this so we can monitor for acceptable use on link names. Not being an API person, I was hoping to be able to use the CLI to generate the report to a CSV that I could download via scripting. I have tried a lot of the options and been over the man pages but cannot seem to get this working.
As an Enterprise customer, I contacted box support but their only response has been, "we don't provide architectural support" and offering to sell me a consulting package. Neither of which is what I have asked for.
So does anyone no if the CLI will do this and if so could you share the arguments you passed to it? If not how have you gone about automating reports?
Thanks,
Bill
-
Hi :
The Box CLI leverages the same API that’s available to the rest of us, and is documented at https://developer.box.com/reference. Even if you don’t write code, that’s a useful reference to know what’s possible.
Unfortunately, Box doesn’t provide an API to generate reports. There is a Box Pulse idea along those lines: https://pulse.box.com/forums/909778-help-shape-the-future-of-box/suggestions/35982049-ability-to-create-box-reports-by-api
The events referred to in the Box Pulse response are available via the Box CLI: see https://github.com/box/boxcli/blob/master/docs/events.md However, turning that into the equivalent of the report you want is probably going to involve a fair bit of post-processing.
Hope that helps, at least a little.
Ian Crew
UC Berkeley
-
Thanks Ian. I did not know there was a place to recommend features/vote! I will dig into it some more. We actually have the Splunk Box plugin but it doesnt seem to be getting collab info. I will check that as well. Box tells me there is no way to get the CLI or API to generate reports as well. Seems like something people would want so hopefully they will implement this or at least add it as an automation action.
Please sign in to leave a comment.
Comments
2 comments