There are two approaches to solve the original question.
Create a custom connector - where @Carlos A-M was heading. Then you need a public API wrap - which Carlos suggested Azure Function as a location for that.
Use Power Automate to get the data for you, then you have to deal with the response which has a high likelihood of being in JSON - and that's where @SeaDude went with his response.
I went #2, and didn't want to pay for premium so I could use the HTTP connector - so I used the workaround posted here: https://henrik-llb.medium.com/power-automate-hack-http-request-to-rest-apis-without-premium-license-da784a5de448. Note that the HTTP connector actually works for me - even without premium. But - I'm worried that if I rely on that, they can shut my solution down any time by disabling that.
Also - premium Power Automate is not very expensive, so, most people would say it's worth the money to not be relying on silly workarounds that are more difficult to maintain.