Endpoint
An endpoint is a network-accessible address or interface through which a service exposes a resource or operation and handles requests and responses.
Learn Go with Pocket-Sized Projects
An HTTP endpoint is a server-accessible interface identified by an HTTP method and request target that processes web requests.
- How it is used
- Provides the client-facing access points for creating, updating, and retrieving resources in a running service.
- How deep it goes
- Defines path–method pairs and works through routing, handlers, request decoding, responses, and tests; defers game storage during initial endpoint setup.
- Examples
- Uses POST /games, PUT /games/{game_id}, curl output, handler tests, and browser-driven habit routes.
- What you can do after
- Build it from scratch in Go by registering a route, implementing its handler, and testing its HTTP response.
Read how Learn Go with Pocket-Sized Projects explains endpoint →
ASP.NET Core in Action, 3e
An endpoint is an addressable application operation associated with a URL pattern that receives a dispatched request and returns a response.
- How it is used
- Defines request-specific responses for web applications and HTTP APIs used by browsers, mobile apps, and other services.
- How deep it goes
- Explains endpoint mapping, handlers, route matching, and selection versus execution; extends basic examples to route templates and parameters.
- Examples
- Uses a plain-text GET response at /, a JSON Person response at /person, and mapped health-check and Razor Page endpoints.
- What you can do after
- Build it from scratch by mapping GET handlers on WebApplication and running the app to serve their responses.
Build Financial Software with Generative AI (From Scratch)
An API endpoint is a network-accessible address or operation at which an API exposes a resource or functionality.
- How it is used
- Organizes file, record, company, search, and OFAC operations into callable HTTP routes.
- How deep it goes
- Walks through endpoint planning, FastAPI routes, tests, prefixes, response models, database calls, and API metadata.
- Examples
- Uses file uploads and retrieval, batch retrieval and search, company overviews, unparsed exception records, and OFAC scan results.
- What you can do after
- Build it from scratch by defining, testing, versioning, and progressively connecting FastAPI endpoints to data-access methods.
Read how Build Financial Software with Generative AI (From Scratch) explains endpoint →
Microsoft Azure in Action
An API endpoint is a network-accessible interface at which an application or service receives requests and returns responses.
- How it is used
- Defines the callable addresses through which applications access functions, serverless workflows, image analysis, or deployed AI models.
- How deep it goes
- Defines an endpoint as a network-accessible address and walks through integration and testing, but leaves deeper API Management configuration out of scope.
- Examples
- Uses an NFT-image copy request, a Computer Vision REST call, and a deployed recommendation model.
- What you can do after
- Operate/configure it in API Management by importing a Function App, inspecting endpoint parameters, and sending a test request.
Spring Security in Action, Second Edition
An endpoint is a network-accessible entry point representing an operation or resource in an application.
- How it is used
- Secures REST routes and limits which authenticated users may invoke them.
- How deep it goes
- Defines routes, demonstrates default authentication, and configures authority checks, but stops short of endpoint implementation internals.
- Examples
- Uses GET /hello, curl requests, HTTP 401 and 403 responses, and READ or WRITE authority assignments.
- What you can do after
- Configure endpoint authentication and authorization with Spring Security’s SecurityFilterChain and authority-based request rules.
Read how Spring Security in Action, Second Edition explains endpoint →
Build AI-Enhanced Web Apps
A network-accessible interface address through which an application receives requests for a particular operation or resource.
- How it is used
- Connects frontend requests to server-side operations and external AI services through application API routes.
- How deep it goes
- Works through Express and Next.js request handlers, including parsing, validation, responses, and streaming; does not detail HTTP protocol internals.
- Examples
- Uses an OpenAI chat handler, a knowledge-base POST route, a text-to-speech stream, and an MCP-enabled chat route.
- What you can do after
- Build it from scratch as a server request handler that validates input, calls a service, and returns a response.
Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
A service endpoint is a network-accessible address through which clients connect to a specific service or resource.
- How it is used
- Directs browsers to static websites and database clients to RDS instances; distinguishes service addresses from REST API routes.
- How deep it goes
- Shows regional website URL selection and RDS endpoint discovery, then uses a database address in an import command.
- Examples
- Uses a regional S3 website URL, an RDS Address-and-Port response, a WordPress SQL import, and image-processing REST routes.
- What you can do after
- Operate/configure it by finding an RDS endpoint, connecting an authorized client, and choosing an S3 website URL for browser access.
Read how Amazon Web Services in Action, Third Edition: An in-depth guide to AWS explains endpoint →
Spring in Action, Sixth Edition
A REST endpoint is an addressable HTTP interface through which a client accesses a resource or operation according to REST principles.
- How it is used
- Exposes backend functionality through HTTP for browser applications and other clients.
- How deep it goes
- Explains controller annotations and works through functional request matching and responses; mentions repository-generated endpoints without detailing their setup.
- Examples
- Uses recently created tacos as a read scenario and GET /hello and GET /bye as functional routes.
- What you can do after
- Apply it via Spring MVC mapping annotations or reactive RouterFunctions to handle HTTP requests.
Read how Spring in Action, Sixth Edition explains endpoint →
Machine Learning Platform Engineering
An API endpoint is a network-accessible interface that receives requests and returns responses according to an API contract.
- How it is used
- Serves trained models through real-time HTTP interfaces within production deployment workflows.
- How deep it goes
- Traces deployment from application packaging through ingress, prediction requests, and metrics.
- Examples
- Uses an income classifier’s /predict endpoint and MLflow’s /health and /invocations endpoints.
- What you can do after
- Operate/configure model-serving endpoints with BentoML and Yatai or MLflow, and inspect requests, health, and metrics.
Read how Machine Learning Platform Engineering explains endpoint →
Pro ASP.NET Core 7, Tenth Edition
An endpoint is an ASP.NET Core object representing a selected application handler together with its metadata and execution logic.
- How it is used
- Maps incoming HTTP requests to response-producing handlers through ASP.NET Core routing.
- How deep it goes
- Explains route selection, pipeline timing, endpoint properties, and inspection; does not detail endpoint construction internals.
- Examples
- Uses equivalent URLs for a Home action, selected-endpoint inspection, a database-backed sum, and a restricted Razor Page.
- What you can do after
- Diagnose/debug with HttpContext.GetEndpoint() to identify the selected handler before it executes.
Read how Pro ASP.NET Core 7, Tenth Edition explains endpoint →
Snowflake Data Engineering
An API endpoint is a network-accessible interface location representing a specific operation or resource of an application programming interface.
- How it is used
- Augments Snowflake pipeline data by retrieving external results through UDFs or stored procedures.
- How deep it goes
- Defines endpoint request-response behavior and details Snowflake access configuration, invocation, JSON parsing, and cleanup.
- Examples
- Uses Yelp bakery reviews, a business alias URL parameter, and a Snowpark Python UDF that returns review excerpts.
- What you can do after
- Apply it via Snowpark Python UDFs or stored procedures to retrieve, secure, parse, and query external API data.
Build Python Web Apps with Streamlit
An endpoint is an API-specific address identifying a particular operation or resource.
- How it is used
- Uses endpoints to direct HTTP requests toward a particular API operation or resource.
- How deep it goes
- Defines endpoint structure and demonstrates parameters and a Python call, without examining endpoint implementation internals.
- Examples
- Demonstrates weather forecast and history endpoints, a dated forecast URL, and OpenAI's chat completions endpoint.
- What you can do after
- Apply it via HTTP URLs or the OpenAI Python client to select an API operation and interpret its response.
Read how Build Python Web Apps with Streamlit explains endpoint →
Automating API Delivery
An API endpoint is a network-accessible interface location through which a client invokes a particular API resource or operation.
- How it is used
- Tracks endpoint changes across API versions to assess consumer compatibility and communicate releases.
- How deep it goes
- Works through diff and breaking-check commands and their output, without detailing endpoint implementation.
- Examples
- Uses a removed categories GET endpoint and a modified products GET endpoint, then checks the removal error.
- What you can do after
- Diagnose/debug with it by comparing OpenAPI versions, identifying removed endpoints, and checking whether a change breaks consumers.
Quarkus in Action
A REST endpoint is a network-accessible resource interface that handles HTTP interactions according to REST conventions.
- How it is used
- Exposes HTTP operations for a generated greeting and a car-reservation service.
- How deep it goes
- Shows an annotated GET implementation, HTTP test assertions, and extension choices; the generated endpoint handles only one call.
- Examples
- Uses GET /hello, a test checking status and body, and reservation operations for available cars and bookings.
- What you can do after
- Apply it via Quarkus REST annotations, then test its HTTP response with REST Assured.
Go in Action, Second Edition
An HTTP endpoint is a network-accessible interface identified by an HTTP method and resource location that handles client requests.
- How it is used
- Uses endpoints to test HTTP request handling and expose read-only article data through an API.
- How deep it goes
- Works through handlers, routing, status codes, test servers, and an injected read interface; does not develop deployment procedures.
- Examples
- Demonstrates /hello GET and POST responses, a rejected PUT request, and a read-only /articles route with a count parameter.
- What you can do after
- Build it from scratch with net/http handlers and ServeMux, then test handler responses and routes with httptest.
Grokking AI Applications
A network-accessible address exposed by an API for receiving requests to perform an operation or provide data.
- How it is used
- Uses an endpoint to let external applications call an application’s logic through an API.
- How deep it goes
- Defines requests, parameters, authentication, and responses, then demonstrates a POST route without detailing HTTP internals.
- Examples
- Demonstrates a Langflow flow and a POST /generate-email route returning structured customer-email JSON.
- What you can do after
- Operate/configure a local FastAPI service and test its endpoint with curl.
Django in Action
An API endpoint is a network-accessible interface location that receives requests and returns API responses.
- How it is used
- Deploys API endpoints as Django views that inspect requests and perform requested actions.
- How deep it goes
- Explains routes, arguments, lookups, serializers, filtering, and versioning, but does not detail HTTP protocol internals.
- Examples
- Demonstrates promoter lookup, venue retrieval, computed slugs and URLs, venue listings, and name-prefix filtering.
- What you can do after
- Build API endpoints in Django Ninja for retrieving, listing, filtering, and serializing model objects.
Secure APIs
An API endpoint is a network-accessible interface location that exposes one or more API operations.
- How it is used
- Uses endpoints as design units for exposing API operations and as observability targets for detecting abuse.
- How deep it goes
- Defines endpoints, explains an enumeration attack, and recommends design checks without descending into endpoint implementation internals.
- Examples
- Illustrates endpoints with Peloton's user-search and workout-details operations and their repeated-call enumeration pattern.
- What you can do after
- Evaluate/understand endpoint designs and diagnose/debug repeated-call patterns that may indicate object enumeration.
ScyllaDB in Action
An API endpoint is a network-accessible path or interface through which an application receives requests and returns responses.
- How it is used
- Exposes restaurant-review operations through HTTP paths connected to Python functions and database queries.
- How deep it goes
- Defines endpoints and implements basic GET and POST flows, but stops short of complete API design and production error handling.
- Examples
- Uses /, /articles, cURL requests, article JSON, author lookup, and returned restaurant-review records.
- What you can do after
- Build it from scratch with Flask, then extend routes to read and write ScyllaDB-backed application data.
Contract Testing in Action
An API endpoint is a network-accessible operation at a specified URL and method through which a client interacts with an API.
- How it is used
- Uses endpoints as client-facing boundaries for retrieving and inserting movie data and for testing API interactions.
- How deep it goes
- Explains routes, parameters, responses, errors, and startup, while noting that real projects require additional error handling and unit tests.
- Examples
- Demonstrates movie collection and lookup routes, a 404 response, and a search-suggestions endpoint tested through Pact.
- What you can do after
- Build it from scratch by defining operations, registering routes, importing data, starting a server, and testing provider interactions.
gRPC Microservices in Go
A gRPC endpoint is a network-accessible interface through which a client communicates with a gRPC service.
- How it is used
- Exposes Order creation to gRPC clients and identifies the Payment service address used for an outbound call.
- How deep it goes
- Works through server registration and a Create handler; configures a Payment endpoint URL but defers its automatic discovery.
- Examples
- Shows an Order Create handler, grpcurl testing, PAYMENT_SERVICE_URL configuration, and a Collector endpoint for metrics.
- What you can do after
- Build it from scratch by registering an Order gRPC handler, mapping its request to application logic, and configuring an outbound Payment address.
Building Web APIs with ASP.NET Core
An endpoint is a network-accessible entry point through which a web API exposes an operation or resource.
- How it is used
- Exposes web API operations and resources through client-accessible HTTP entry points.
- How deep it goes
- Demonstrates routes, Minimal API and controller organization, authorization, and OpenAPI grouping, but not endpoint runtime internals.
- Examples
- Uses Account/Register, /auth/test/4, controller-based groups, and SwaggerUI endpoint tags as concrete examples.
- What you can do after
- Build it from scratch via ASP.NET Core routes or controllers, secure operations, and organize their Swagger/OpenAPI documentation.
Read how Building Web APIs with ASP.NET Core explains endpoint →
.NET in Action, Second Edition
An endpoint is a network-accessible interface that receives requests and returns responses for a defined operation or resource.
- How it is used
- Exposes air-conditioner sensor measurements to controllers and site owners through an ASP.NET Core web API.
- How deep it goes
- Implements routing, parameter binding, response modeling, JSON output, and an HTTP integration test.
- Examples
- Uses /measure/TIJ1/1 to return the latest exhaust-air, coolant, and outside-air measurements.
- What you can do after
- Builds and tests a C# ASP.NET Core endpoint that returns typed measurement data.
Learn Haskell by Example
An API endpoint is a network-accessible operation identified by a route and HTTP method at which an API accepts requests.
- How it is used
- Defines Servant API operations, including routes, HTTP verbs, request bodies, and response types.
- How deep it goes
- Specifies endpoint composition and validation, but defers detailed explanation of DataKinds and TypeOperators.
- Examples
- Uses simple GET routes, JSON responses, POST bodies, and a todo API with entries, addition, and toggling.
- What you can do after
- Build it from scratch by declaring Servant endpoints as composable Haskell types.
Effective Data Analysis
An API endpoint is a specific network-accessible address at which an API receives requests for a particular resource or operation.
- How it is used
- Supports regularly refreshed public-data analyses by querying filtered records for stakeholder-facing model assessment.
- How deep it goes
- Shows portal-generated URL construction and Python JSON querying, without detailing API design or protocol internals.
- Examples
- Uses date-filtered NYC 311 rat-sighting records as the concrete endpoint example.
- What you can do after
- Apply it via Python and requests to retrieve date-filtered JSON records for a refreshable extraction pipeline.
Python Concurrency with asyncio
- How it is used
- Uses addresses to expose REST resources and application operations to clients such as browsers, mobile applications, and command-line tools.
- How deep it goes
- Explains resource paths and implements one GET route, while deferring the full details of REST.
- Examples
- Uses customer collection, singleton, and nested favorites paths, plus an aiohttp time endpoint tested with cURL.
- What you can do after
- Build it from scratch with aiohttp by declaring a route, handling its request, returning JSON, and starting the server.
Read how Python Concurrency with asyncio explains endpoint →
Related concepts
- contractpart of · An API contract is a specification of the operations, data, and behavioral expectations that govern interactions between software components.
- managed APIused by · A managed API is an interface to a remotely hosted service whose provider operates the underlying software and infrastructure.
- base pathconfigured by · A base path is the common URL or URI path prefix under which an application, API, or set of resources is exposed.
- request messageused by · An HTTP request is a message sent by a client to a server that specifies a method and target and may include headers and a body.
- health check endpointincludes · A health check endpoint is an API endpoint that reports whether an application or service is operating correctly or ready to handle requests.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.