An API endpoint is a specific address, usually a URL, where an application programming interface receives requests and sends back a response. If an API is the whole service that lets two programs talk, an endpoint is one particular door into it, each one tied to a single job. You send a request to an endpoint, the service does the work, and it returns the result, often as structured data. Knowing what an endpoint is, and how it differs from the API as a whole, clears up a lot of early confusion. Here is how endpoints work and how to read one.
How an endpoint works
Think of an endpoint as a labeled counter at a service desk. One counter handles new orders, another handles pickups, another handles returns. You walk up to the right counter, state your request, and get a response. An API endpoint is the same idea expressed as a URL: each address handles one kind of request.
When your program contacts an endpoint, it sends a request that names the endpoint, includes a method that says what action you want, and sometimes carries data. The service reads all of that, performs the work, and replies. Because the address and the action are explicit, both sides know exactly what is expected.
If the broader concept of programs talking over the web is new, our explainer on what a REST API is gives the foundation that endpoints build on.
Endpoint plus method
A single endpoint URL can support several actions, and the method you use decides which one happens. This is why the same address can both read and change data without contradiction.
| Method |
Typical action |
Plain meaning |
| GET |
Read |
Give me this thing |
| POST |
Create |
Make a new thing here |
| PUT or PATCH |
Update |
Change this thing |
| DELETE |
Remove |
Delete this thing |
So an endpoint for a user record might return that user with a read request and update it with an update request, all at the same URL. Reading an endpoint means reading both the address and the method together.
Endpoint vs API
The clearest way to separate the two is the menu analogy. The API is the entire menu of what a service can do. An endpoint is one dish on that menu. A weather service might be one API with separate endpoints for the current conditions, the hourly forecast, and the weekly outlook.
- The API is the whole agreement and collection of capabilities a service exposes.
- An endpoint is one specific address within that API for one specific task.
- A request is a single call you make to an endpoint using a chosen method.
Keeping these straight helps you read documentation, where each endpoint is usually listed with its URL, its supported methods, and the data it expects.
Common mistakes
- Confusing the endpoint with the whole API. The endpoint is one entry point; the API is the full set.
- Using the wrong method. Sending a read where a create is expected returns an error or nothing useful.
- Ignoring required data. Many endpoints need specific fields; omitting them fails the request.
- Hardcoding endpoints that change. Read the documentation, since services version and move endpoints over time.
FAQ
What is the difference between an API and an endpoint?
An API is the entire service and its set of capabilities; an endpoint is one specific address within that API that handles one task.
Is an endpoint always a URL?
For web APIs, yes, an endpoint is typically a URL. The term can apply more loosely elsewhere, but on the web it is an address you send requests to.
Why does the same endpoint do different things?
The method attached to your request decides the action. A read, create, update, and delete can all target the same address.
How do I know what an endpoint expects?
Check the API documentation, which lists each endpoint URL, the methods it supports, and the data it requires.
Where to go next
Build the foundation with What Is a REST API in 2026, see where requests are answered in What Is a Server in 2026, and learn the client side in What Is a Client in 2026.