# Endpoint

A specific addressable interface location where a client can interact with a software service using defined operations and messages.

- Type: term
- Domain: Engineering & architecture
- Level: Foundational
- Last reviewed: 2026-09-23
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/endpoint/>)

## What it means

An endpoint is a concrete point of interaction exposed by an API or network service. In an HTTP API it is commonly described by a server address, path, and supported method, such as GET /orders/\{id\}; the path alone does not fully define the operation.

## Why it matters

Endpoints turn an API contract into callable capabilities. Clear boundaries and consistent naming help consumers discover operations, apply authorization correctly, diagnose failures, and understand which behavior can change independently.

## When to use it

Use the term when identifying where and how a client invokes a specific service operation. Use resource, route, URL, or server when that narrower concept is what matters; they are related but not interchangeable with endpoint.

## How it works

1. Choose the capability or resource that the service will expose.
2. Assign an address and the protocol operation or method accepted at that address.
3. Define parameters, request content, responses, errors, security, and usage constraints.
4. Route matching client requests to the implementation responsible for the operation.
5. Document, test, observe, version, and eventually deprecate the endpoint as part of the API contract.

## A practical example

An inventory service exposes GET /products/\{sku\}/availability. The same path with PUT would be a different operation, so documentation specifies the method, identifier format, authorization, response schema, error codes, and rate limits together.

## Where it breaks

The word is used loosely across HTTP, messaging, and networking, so an endpoint name alone may not identify the protocol or operation. Too many narrowly scoped endpoints can produce chatty integrations, while broad endpoints may mix unrelated responsibilities.

## Common mistakes

- Treating a path by itself as a complete endpoint while ignoring the HTTP method and server context.
- Using endpoint, API, server, and URL as interchangeable terms.
- Designing endpoints around database tables without considering consumer workflows.
- Changing endpoint behavior while leaving its documented contract unchanged.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/endpoint/#visualization-endpoint>)

## Sources

1. [OpenAPI Specification: Paths Object](<https://spec.openapis.org/oas/latest.html#paths-object>) — OpenAPI Initiative · Technical specification
2. [API](<https://developer.mozilla.org/en-US/docs/Glossary/API>) — MDN Web Docs · Official technical documentation

## Related topics

- [Application Programming Interface \(API\)](<https://wiki.soroush.uk/topic/application-programming-interface/>)
- [HTTP Method](<https://wiki.soroush.uk/topic/http-method/>)
- [Request and Response](<https://wiki.soroush.uk/topic/request-and-response/>)
