What are typical HTTP methods and endpoints for the Address resource in a REST API?

What are typical HTTP methods and endpoints for the Address resource in a REST API?

• A. Create: POST /addresses; Read: GET /addresses/{id}; Update: PUT/PATCH /addresses/{id}; Delete: DELETE /addresses/{id}; List: GET /addresses with filters
• B. Get: GET /addresses; Create: POST /addresses/{id}
• C. Create: POST /users; Read: GET /users
• D. All operations via SOAP

Answer: (A)

In REST design, resources are addressed by URLs that distinguish a collection from a single item, and actions map to HTTP verbs. For an Address resource, the conventional pattern is to create with a POST to the collection endpoint /addresses. To read a specific address, fetch it with GET /addresses/{id}. To update, send PUT or PATCH to /addresses/{id} (PUT usually replaces the whole resource, while PATCH applies partial changes). To delete, issue DELETE to /addresses/{id}. To retrieve multiple addresses, use GET /addresses, often with query parameters to filter results (for example, /addresses?city=Seattle or /addresses?state=CA). This arrangement mirrors standard REST semantics: the URL structure shows whether you’re working with the collection or a single resource, and the HTTP method communicates the action. Other patterns—such as POST to /addresses/{id} for creation, using a different resource like /users for an addresses topic, or relying on SOAP—don’t fit typical RESTful CRUD on a distinct resource like addresses.

In REST design, resources are addressed by URLs that distinguish a collection from a single item, and actions map to HTTP verbs. For an Address resource, the conventional pattern is to create with a POST to the collection endpoint /addresses. To read a specific address, fetch it with GET /addresses/{id}. To update, send PUT or PATCH to /addresses/{id} (PUT usually replaces the whole resource, while PATCH applies partial changes). To delete, issue DELETE to /addresses/{id}. To retrieve multiple addresses, use GET /addresses, often with query parameters to filter results (for example, /addresses?city=Seattle or /addresses?state=CA).

This arrangement mirrors standard REST semantics: the URL structure shows whether you’re working with the collection or a single resource, and the HTTP method communicates the action. Other patterns—such as POST to /addresses/{id} for creation, using a different resource like /users for an addresses topic, or relying on SOAP—don’t fit typical RESTful CRUD on a distinct resource like addresses.