Hi @joseluizferreira - Thanks for your post! This is a really interesting use case. As you point out, the instrumentation data API doesn't currently support collaborator access, only content ownership.
Are the applications you're looking to gather data on all owned by the same publisher account, or multiple accounts?
If they're all owned by the same publisher, it could be fairly simple for that app owner to set up a scheduled R Markdown ETL process that gathers their own instrumentation data, filters it down to the applications their interested in sharing with this collaborator, and pushing that filtered data out as a published Pin or R Markdown output data file which can then be directly access restricted to the collaborator like any other piece of content on Connect.
If the apps are owned across several publisher accounts, you could potentially follow a similar R Markdown ETL pattern as described above, but with an Administrator API key - being extra careful to filter down for only the application GUIDs that the collaborator should have access to. The use of an Administrator API key would probably take some negotiating, of course, and might be a non-starter entirely depending on what your internal policies are.
I'm happy to write this up in more specific detail if you'd like. I'll also raise this case as a feature request to our product teams as we examine the future of the Connect API work. Thanks so much for sharing. Please let me know if this was useful at all.