liveBook · Manning

Url path

A URL path is the hierarchical component of a URL that identifies a resource or route within its host.

How 3 Manning books explain it

The Design of Web APIs, Second Edition

A resource path is the URI path used to identify a REST resource, including a collection or one of its elements.

How it is used
Maps REST resources and their relationships into meaningful HTTP request targets.
How deep it goes
Explains syntax, hierarchy, parameters, naming, shortening, OpenAPI description, and compatibility, while deferring fine-grained data modeling.
Examples
Uses /products, /products/{productReference}, /accounts/{accountId}/transactions, banking paths, and library-path correction exercises.
What you can do after
Apply it via HTTP and OpenAPI to design, document, review, and evolve predictable collection and element paths.

Read how The Design of Web APIs, Second Edition explains url path →

ASP.NET Core in Action, 3e

An HTTP path identifies the resource or resource location targeted by an HTTP request.

How it is used
Locates the resource that an HTTP request asks a web application to handle.
How deep it goes
Defines path composition and demonstrates routing it with MapGet, but stops short of detailed HTTP protocol internals.
Examples
Uses /account/manage as a path example and maps the root path / to a Hello World response.
What you can do after
Apply it via ASP.NET Core's MapGet function to associate a GET request with a URL path and response.

Read how ASP.NET Core in Action, 3e explains url path →

Automating API Delivery

A URI path is the path component of a uniform resource identifier that identifies a resource or resource hierarchy in an API.

How it is used
Enforces consistent API path versioning during automated API linting.
How deep it goes
Descends from resource identification to JSONPath Plus selection, regular-expression matching, testing, and Spectral execution.
Examples
Uses product-catalog-v3.oas.yaml, yq conversion, jpp evaluation, and a version-matching Spectral ruleset.
What you can do after
Apply it via Spectral to detect API paths that do not begin with a numeric version segment.

Read how Automating API Delivery explains url path →

Related concepts

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.