endpoint
/ END-poynt /
An endpoint is one specific address an API exposes for one specific action. If an API is the whole menu, an endpoint is a single line on it: a URL like /users that you can hit to get something done. Send a request to that address, and the API does that one job and replies.
Each endpoint usually pairs a path with a verb that says what you want to do: GET /users means 'give me the list of users,' POST /users means 'create a new user,' GET /users/42 means 'show me user number 42.' Same address, different verb, different action — like asking the same desk to either show you a record or file a new one.
So an API is really just a tidy collection of endpoints, each one a small, named door into a specific capability. Learn an API and you're mostly learning its list of endpoints: what doors exist, and what each one does.
GET /users → list everyone POST /users → create a new user GET /users/42 → fetch user #42
Three endpoints on one API: same paths, different verbs, different jobs.
The verb (GET, POST…) is half the meaning — GET /users and POST /users are two different endpoints in practice.