My use case is the following: I have a Streamlit application that depends on a job that is scheduled in Orchest. It runs every 6 hours, but I would like to make it easier for the users to update the data by setting a trigger for the job inside the application. I'm planning to use the orchest routes

/jobs

and

/jobs/{job_uuid}/runs/trigger

. Is there a better way to do what I'm planning to? If this is the best solution, how can I authenticate my requests to be able to make them inside orchest?

That use case makes sense! We're planning to add a dedicated public REST API to make triggering job runs easier. See the roadmap. In the meantime you could "hack" around it by taking inspiration from this example that shows how to currently automate certain Orchest UI actions through HTTP API calls (it also includes a snippet about how to handle authentication): https://github.com/orchest/api-examples It's not really recommended because it's making use of unstable APIs that are subject to change, but it would allow you to do now what you're trying to do.

Thank you very much @Rick Lamers. It would be awesome to have a public API. Thanks for the example as well, I will adapt it to my usecase 🙂