Let’s say I’m using Express and writing my user login/registration system. It’s connected to a database and gives out a JWT token when the user has been created or verified, etc.Now, my understanding is that any time you develop a system that is meant to respond to HTTP (axios/fetch) requests a certain way, you are technically developing an API.Sure, you can have an API that does some cool fancy stuff and sends back transformed images or machine-learning type responses to things. But as far as I’m aware, as long as you’re responding to a request, you’ve made an API.So.... is a login/register system an API? Because you are writing a backend to respond to HTTP requests that are asking to login? Could a developer safely refer to their user authentication flow as their “Login API”, even if it’s kind of silly to do so?
Submitted January 18, 2020 at 07:08PM by NelsonShepherd
No comments:
Post a Comment