@sibertFeb 24.2022 — #> @kiwis80#1642830 Can someone start me off when how I should be doing this.
My experience is that there are no consensus. Not even close. And you can do this in many ways. But there are at least 4 main ways to create an API.
1. Half ready solutions like **[GraphQL](https://graphql.org)**. An ORM sort of.
2. Do-it-yourself REST.
3. gRPC
4. PostgREST (addition to Postgresql - Also an ORM type of solution)
The basic is to send a html request. https://api3.go4webdev.org/usr/all and the API get all users. And the most common return of an API is JSON.
In order to learn, I chose to do it the hard way. The documentation of my journey, you can find **[here](https://crud.go4webdev.org)**. And of course I did it even harder not choosing PHP. Some should say it was even easier. :-)
To answer your question: There are many ways to skin a cat (Mark Twain)
@ClaudeSjDevinHenryMar 09.2022 — #All API clients must authenticate with OAuth2. OAuth is an open protocol that allows secure authorization from web, mobile, and desktop applications.
Also, Reddit’s OAuth API is only accessible via HTTPS, not HTTP.
Most of the wrappers / libraries mentioned [voojio](https://voojio.com/chatroom/omegle) next in the article will have clear instructions on how to authorize via [shagle](https://shagle.download) OAuth2.
@HereturbiesWaltMar 11.2022 — #When programmers decide to make some of their data available to the public, they “expose endpoints,” meaning they publish a portion of the language they’ve used to build their program. Other programmers can then pull data from the application by building URLs or using HTTP clients (special programs that build the URLs for you) to request data from those endpoints.
Endpoints return text that’s meant for computers to read, so it won’t make complete sense if you don’t understand the computer code used to write it.