What you describe sounds like a perfect use of Creo.
Here's a tutorial on connecting to the Spotify REST API which returns JSON: http://blog.creolabs.com/2015/12/04/custom-view-and-real-data/ The endpoint in the example is https://api.spotify.com/v1/search/?q=adele&type=album to give you a flavor.
But. You should be aware that at present it isn't possible to take contents from input fields in Creo and pass them to the http client's properties. So for example you couldn't have a "my search box" input field together with a search button that would take the contents of "my search box", perform a search against your news service and return results.
This is 'dynamic properties' and if you hunt around the forum it has been scheduled for the next beta release. Similarly when you get results back into say a list-view or table, you will need to pass record IDs from your table into a detail screen so the detail screen knows which record(s) to display - @marco has kindly offered to do a blog post on how this can be done, around the time Creo b5 is released.
And yes, Creo does seem to be awesome. ;-)