Word setBuild Basics
Build Basics / Standard term
Endpoint
An endpoint is one specific address inside an interface that handles a single kind of request, such as the address you call to fetch recent messages or the one you call to post a new item.
An endpoint is one specific address inside an interface that handles a single kind of request, such as the address you call to fetch recent messages or the one you call to post a new item. A single service usually exposes many endpoints, each one doing a distinct job. Picture a to-do app: one endpoint at /tasks returns the open items, another at /tasks accepts a new item when you send it, and a third at /tasks/4 deletes the task with that identifier. The address plus the kind of action you send tells the server exactly which job to run and what to send back.
Builder example
When you tell an AI assistant to wire your app to a service, you are pointing it at endpoints. A password-reset feature might call one endpoint to send the reset email and a second to confirm the new password. If you ask for the wrong endpoint, hit one that no longer exists, or send the wrong kind of action, the call fails or quietly does nothing. Naming the exact endpoint and what it should return keeps the assistant aimed at the right address.
Common confusion: An endpoint is one address within an interface; the interface is the whole set of addresses a service offers. A weather Application Programming Interface (API) is the full service, while the address you call for today's forecast is a single endpoint inside it.