In your screenshot, I believe I see a web service that uses a password as a parameter input (that doesn’t change, right?) and provides a token among the result. This token is the one that you need to reuse across all the other API calls you’re making in that experience. Is this correct?
If so, you can schedule the experience to call that “sign-in” API first when launching the experience, or on a regular basis (every day, every first day of the month, …) and then have all your other APIs use this response token as their parameter inputs.
This procedure is very similar to the one described in this article: https://support.intuiface.com/hc/en-us/articles/360030790812-Control-LED-light-bars-on-IAdea-XDS-1088
Let me know if that answers your needs.