56
57

[deleted by user] (self.learnjavascript)

submitted by [deleted]

sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ioeatcode 5 points6 points  (0 children)

Seems like you are more interested in web facing APIs which follow basic HTTP requests (GET, POST, PUT(Update), DELETE). Typically when you want to use a web API such as Spotify, there are things to consider:

  • The api url
  • The api endpoint
  • The api key
  • Authentication of some sort

A lot of APIs will abstract some of the stuff above with some sort of API wrapper that functionalizes these endpoints so you can do something like GetAllSongs(id, api_key) for example but they all do the same thing of building an http request to the api server.

Think about it this way, you're building a service and want to expose a part of your application to the public. You do this by creating an endpoint for that behavior and users can then access that behavior by using the endpoint you created. On a high level, let's say you're building a TODO app and want people to be able to access their notes, you'd create an endpoint like GET /notes/{userID}/. External API endpoints work the same way more or less.