liveBook · Manning

Url path

Also called request path

A URL path is the hierarchical component following the authority that identifies a resource or route within the addressed 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
Identifies REST resources so consumers can address collections and elements and pair them with HTTP operations.
How deep it goes
Works through naming, hierarchy, identifier scope, OpenAPI declarations, and compatibility; distinguishes paths from underlying storage.
Examples
Uses product collections, account transactions, customer addresses, and an OpenAPI product path to test path choices.
What you can do after
Apply it via OpenAPI 3.1.0 to describe predictable collection and element paths with required path parameters.

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 →

Also covered in

What to know first

Related concepts

Questions about url path

What is url path?

A URL path is the hierarchical component following the authority that identifies a resource or route within the addressed host.

Which Manning books explain url path?

The Design of Web APIs, Second Edition, ASP.NET Core in Action, 3e and Automating API Delivery.

What should I know before learning url path?

Manning books that teach url path usually introduce HTTP request, JSON, HTTP GET and server first.

What kinds of url path are there?

Kinds of url path include hierarchical identifier and nonhierarchical path.

What are the parts of url path?

Url path includes route parameter and path-level versioning.

What is url path also called?

Url path is also called request path.

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.