Which REST principle emphasizes that clients interact with resources via a uniform interface using standard HTTP methods and URIs?

Which REST principle emphasizes that clients interact with resources via a uniform interface using standard HTTP methods and URIs?

• A. Stateless
• B. Code on Demand
• C. Uniform Interface
• D. Cacheable

Answer: (C)

Uniform Interface is the REST principle that enforces a consistent way for clients to interact with resources. It means clients address resources with URIs and use standard HTTP methods to manipulate them (for example, retrieving with GET, creating with POST, updating with PUT or PATCH, and deleting with DELETE). The resources are represented in standard formats like JSON or XML, and the same set of rules applies across all resources, which decouples the client from the server’s internal workings. This consistency makes APIs predictable and easy to use, and it enables the architecture to evolve without breaking existing clients. Other REST constraints exist as well but describe different aspects: Stateless means each request carries all needed information; Code on Demand is optional and allows servers to send executable code to clients; Cacheable specifies that responses can be cached to improve performance. They are important, but they don’t define the way clients uniformly interact with resources using standard methods and URIs.

Uniform Interface is the REST principle that enforces a consistent way for clients to interact with resources. It means clients address resources with URIs and use standard HTTP methods to manipulate them (for example, retrieving with GET, creating with POST, updating with PUT or PATCH, and deleting with DELETE). The resources are represented in standard formats like JSON or XML, and the same set of rules applies across all resources, which decouples the client from the server’s internal workings. This consistency makes APIs predictable and easy to use, and it enables the architecture to evolve without breaking existing clients.

Other REST constraints exist as well but describe different aspects: Stateless means each request carries all needed information; Code on Demand is optional and allows servers to send executable code to clients; Cacheable specifies that responses can be cached to improve performance. They are important, but they don’t define the way clients uniformly interact with resources using standard methods and URIs.