Any tips or tutorial for using Postman in fitbit apps

[RustyKeyboard]

I've read many topics where developers were not able to use await/fetch for remote http (not https) API in Fitbit apps.  I'm trying to query a Rest News API.  My complimentary account only allows http and not https requests.  I have written an html page that will query and receive correct responses from this API on Firefox, Safari (on iPhone) and MS Edge (the latter didn't work initially, but now does).

When using same code in Fitbit app, there is no response to fetch/await/http.  I understand that in Fitbit these can only be used to access https endpoints and resources.

The API support staff recommended that I use Postman.  I am totally clueless about Postman.  Since I can access the API via browsers, now I'm wondering if that will make any difference in my Fitbit app.

Will Postman allow me to access an http API and make responses available to my Fitbit app?

Thanks

[Gondwana]

It's possible that info about the Web API and Device SDK is being confused. Postman is often recommended as a way of experimenting with Web API calls, but I don't think it's of any use within the Device SDK.

If you really need to get insecure http data into the Device API, you could do it by writing and hosting a web server on your phone. This can be accessed via http as 127.0.0.1 from the Device API, and could access and transfer the REST data. Developing such a server isn't trivially easy, and it would need to be running on the phone of anyone using your app.

[Gondwana]

Addendum: you could actually host your server on any device that's accessible from the Fitbit Device API. If your LAN has a computer that can serve using a non-self-signed certificate, you could use that via https. If you've got a web hosting account on the internet, that would also provide https and could be reached from anywhere.

[RustyKeyboard]

@Gondwana , thanks for the responses.

All of that is beyond my ability.  I'll just have to stick to things that are more straightforward.