Roadmap › ASP.NET Core Web API & REST › Module: REST Fundamentals
Lessons in this course (15)
1. REST principles and resource design
Basic★ Must knowLesson 1 of 15
| Action | Method | URI | Success status |
|---|---|---|---|
| List | GET | /api/orders?status=open&page=2 | 200 |
| Get one | GET | /api/orders/42 | 200 / 404 |
| Create | POST | /api/orders | 201 + Location header |
| Replace | PUT | /api/orders/42 | 200 / 204 |
| Partial update | PATCH | /api/orders/42 | 200 / 204 |
| Delete | DELETE | /api/orders/42 | 204 |
| Sub-resource | GET | /api/customers/7/orders | 200 |
Guidelines: nouns not verbs (/orders, not /getOrders), plural collections, hierarchy for relationships, query string for filtering/sorting/paging, consistent casing (kebab-case paths, camelCase JSON), version the API, use standard status codes.
Idempotent methods give the same result if repeated: GET, PUT, DELETE, HEAD, OPTIONS. Safe methods don't change state: GET, HEAD, OPTIONS. POST is neither; PATCH is not guaranteed idempotent.