Uniform interface
A uniform interface is a REST architectural constraint requiring consistent resource identification and standardized semantics for client-server interactions.
Building Web APIs with ASP.NET Core
A uniform interface is a REST constraint defining standardized resource identification, manipulation, messages, and hypermedia controls.
- How it is used
- Guides the design of RESTful responses so clients can identify resources and discover available actions.
- How deep it goes
- Defines four guiding principles and works through response DTOs and JSON, without prescribing a REST-mandated response format.
- Examples
- Uses a board-game URI, GET and DELETE requests, and a JSON collection response containing data and a self link.
- What you can do after
- Build it from scratch with ASP.NET Core response DTOs that pair requested data with structured links.
Read how Building Web APIs with ASP.NET Core explains uniform interface →
The Design of Web APIs, Second Edition
The uniform interface constraint is a REST constraint requiring a consistent and standardized interface for interacting with resources.
- How it is used
- Structures API capabilities around resources and HTTP methods to make operations predictable, usable, secure, extensible, and interoperable.
- How deep it goes
- Explains the constraint, applies it to input locations and resource design, and connects it to flexibility without detailing implementation internals.
- Examples
- Uses transaction search paths and query parameters, resource-oriented operation design, and request input-location comparisons.
- What you can do after
- Apply it via HTTP resource design and input placement to create APIs that consumers can understand, use, and evolve.
Read how The Design of Web APIs, Second Edition explains uniform interface →
Related concepts
- RESTpart of · REST is an architectural style for distributed hypermedia systems that organizes interactions around resources and representations through constraints including a uniform interface, stateless communication, cacheability, and layered components.
- HTTP methoduses · An HTTP method is a standardized operation token in an HTTP request that specifies the intended action on a resource.
- resourceuses · An API resource is a conceptual entity or target exposed through an interface and addressable for access or manipulation.
- hypermediauses · Hypermedia is content or information structured with links or controls that enable navigation to related resources or actions.
- self-descriptive messageshas part · Self-descriptive messages contain all information required for a recipient to understand and process them correctly.
- operation flowused by · An operation flow is an ordered sequence of API operations that an application invokes to obtain information or complete a process.
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.