A big hotel desk has separate counters: one for check-in, one for luggage, one for taxis. Each API request goes to its own counter too.
In a busy hotel, the front desk isn’t one counter. There’s a check-in counter, a luggage counter and a taxi counter. Go to the right one and you’re served straight away.
An API works the same way. Each endpoint is one specific address that handles one kind of request. One for looking up orders, another for creating them, another for cancelling.
What they look like
/weather/todaygives today's forecast/orderslists your orders/orders/123gives one particular order
The kind of request matters too
The same endpoint can do different things depending on how you ask: “get” to read, “post” to create, “delete” to remove. It’s like saying “I’d like to check in” versus “I’d like to check out” at the same counter.
What it isn’t
It isn’t a separate app. All the endpoints together make up one API.
Where the comparison breaks down
Hotel counters have staff who can help if you’re at the wrong one. Ask the wrong endpoint and you just get an error, often a 404.
How the words fit together
An API is made of endpoints. You call them with an API key. They reply with a status code and some data, often as JSON.
Endpoints look like web addresses, for example /orders or /weather/today. Each one does one job.

When you'll hear it
“Which endpoint should I call?” Which exact address on their API handles what I'm trying to do?
“That endpoint is deprecated.” That address still works for now, but it's being retired, so stop using it.
“The endpoint returns a 404.” Nothing exists at that address, so the request went to the wrong counter.
“Which parts of their API do we actually need? Are any of them being retired soon?”

Try it yourselfReady to use it? The exact commands are on my other site, devcmds: Call an API from the terminal ↗


