> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/a/api-endpoint.md). # API Endpoint An API endpoint is a specific URL or URI where an API receives requests. Each endpoint corresponds to a particular resource or operation that the API exposes. For example, `GET /api/users` might return a list of users, while `POST /api/users` creates a new user. Endpoints are the touchpoints through which external clients interact with a backend service. They are defined by a combination of the HTTP method (GET, POST, PUT, DELETE, etc.) and the path. Well-designed endpoints follow consistent naming conventions and map logically to the underlying data model. In API gateway architectures, endpoints are the primary unit of routing configuration. The gateway maps incoming requests to the correct backend service based on the endpoint path, method, and other criteria such as headers or query parameters. This makes endpoint management central to API governance, security enforcement, and traffic control. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.serverlessapigateway.com/glossary/a/api-endpoint.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.