API endpoint for Collections

[JSNelson08]

My team currently uses the API to call a large number of workflows via a Python based scheduler process.  We use this currently by having ~10 users in a single subscription (Private Studio).  

All of the Private Studio sites on the Alteryx help state that they are going away in the near future to be replaced by individual studios and Shared Collections.  

From our testing, this would kill our processing as we cannot have an API for 1 Private Studio call workflows from a different private studio even if they have access through a shared collection.  

Are there plans to adjust the API endpoints in the future to better account for this?

Our IT department is looking to move to the Collections based structure now in preparation for the removal of the current Studio setup, so another question is when the structural update is planned to go into effect (which server version should we expect this?) so that we can get ready to account for this or if we can ask them to back off a little.

Thanks

[MinaGO3]

Curious if there are any updates on this feature @JohnPelletier?

[JohnPelletier]

I need to let @mbaerend take this question and give any updates since I've moved onto a new product, coming soon on the cloud platform.

[mbaerend]

@MinaGO3 @JSNelson08 we are actively working on an API to allow users to call workflows from a different private studio even as long as the asset has been shared with the user via a collection. Currently, we are planning the studio deprecation for some time next year, but please know that estimate is subject to change. We will give you ample notice and recommendations to help with the migration before we deprecate studios. Thank you for your feedback and patience!

[SPetrie]

This shows implemented, but Im not seeing a v3 Jobs endpoint that would let me run a workflow shared with me through a collection. Did this actually get implemented, and how can we run workflows that are in a collection but not owned by us?

Edit: I answered my own question. I found it in the release documentation. I am unable to use it since we are not on 2023.2 yet, but incase anyone else is wondering, thats the version you need.