API for non-devs 101?

[InvisibleJim]

I think you misunderstand. Using client side javascript to make a rest request exposes where the source of the data is. I have seen n00bs who have exposed their entire website content sources including api keys using ajax, and didn't even know that the keys to the kingdom are just outside the door.

I've been struggling to understand how Jamstack sites deal with this - say a Gatsby site hosted in AWS or Azure storage in particular. If I recall, specialised services like Netlify have specific functionality to keep secrets secret this but I'm not getting how the keys should generally be secured when using normal cloud storage.

 

[|tera|]

Let's say a system I need to interface with for updates/changes doesn't have an API. Is there another way to do it?
If it's too broad, please correct me.
Thanks

 

[Hamish McPanji]

Let's say a system I need to interface with for updates/changes doesn't have an API. Is there another way to do it?
If it's too broad, please correct me.
Thanks

You scrape. So similar to an api request, but you request the webpage, then extract the data from the tags that interest you, and generate your own html with the data included

You can load the Web page in your Web browser, view source and search, inspect the tags to see where the data you want is sitting