Hi Corona,

thanks for your answer, even if not using very nice words.

What I get out of it: Beware what unknown data can possibly and in worst case may do and especially in heavy interpreted shell environment.

---

The method was not - like you assumed - to get the full data out of the API, have it locally and pull the needed bits out locally. It was in short looking at the API the only way to get what I need. Digging deeper now into the api documentation revealed other ways to do the same more efficiently.

Maximum efficiency was not my goal. I started with a shell script and at about half completion of the task I realized that the task may be to complex for a shell script and it would have been better to use a scripting language. Now I have a 500 lines Bash script which is implemented fairly well structured and working quite well. I will not rewrite it again if there are not serious issues.

My intention with this question is/was to get feedback is if there are any serious problems I was not aware of.

Since all of that data is JSON data which will get fed into jq for extraction, I do not see much potential trouble ahead.