Hi, this seems like a perfect use case for our new python api,
and in fact it’s a very similar scenario to some of the examples they share as notebooks
in the documentation for it. If you’re not familiar with them, Jupyter notebooks are environments where
you write your python code, run it, and view the results all in the same screen.
You can think of it as your script, text editor and terminal all in one place. Another benefit of the notebook workflow,
is that they can be easily modified as necessary, and shared as a single file.
Having said that, the Jupyter Notebook integration with the python api is completely optional.
You could export your notebook to a .py file, as it’s just standard python code, or write it in your text editor of choice from the start.
This would give you the ability to automate running the script, while still benefitting from the perks of the modern api.
You linked to the guide for the api in your post. Here is one of the notebooks in the documentation that you should take a look at also.
Thank you,
Marvin Perry
