Endpoint

A defined communication boundary where a client can send or receive messages under a protocol and contract.

In an HTTP API, an endpoint is commonly identified by a method and route, such as GET /tasks or POST /tasks. The same path can support several operations, and other systems use queues, sockets, remote procedures, or event topics instead of one web address. Authentication, headers, body schema, status behavior, and version are part of the usable contract.

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.