What is an API endpoint?
An endpoint is a specific URL where an API receives requests for a particular resource or action. For example, /users is an endpoint for working with users. Combined with an HTTP method, an endpoint defines one operation, so GET /users lists users and POST /users creates one. Each endpoint is a doorway into the API.
- An endpoint is a specific URL where an API exposes a resource or action.
- It combines a path with an HTTP method to define one operation.
- Clear, consistent endpoints make an API easy to understand and use.
How endpoints are named
Good REST endpoints use nouns for resources, not verbs, because the HTTP method already carries the action. So you use /orders rather than /getOrders, and let GET, POST, and DELETE decide what happens.
- GET /orders: list all orders.
- POST /orders: create a new order.
- GET /orders/5: get one specific order.
- DELETE /orders/5: delete that order.
Say endpoints should use nouns, not verbs, in REST. Correcting a verb style path like /createUser to POST /users during an interview is a small detail that signals solid API design habits.
Frequently asked questions
How should you name endpoints?
Use nouns for resources and plural names, such as /users and /users/42, and let the HTTP method describe the action rather than the URL.
Can one URL have multiple endpoints?
Yes. The same path can support different HTTP methods, so /users with GET lists users and /users with POST creates one.
Common follow up questions
Related interview questions
Want the full API Design guide?
Read every API Design concept with notes, diagrams, and code in one place. Track your progress as you go.
Open the API Design guide All API Design questions