1.8 KiB
1.8 KiB
Overview
Here is the API that you’ll create:
| API | Description | Request body | Response body |
|---|---|---|---|
| GET /api/todo | Get all to-do items | None | Array of to-do items |
| GET /api/todo/{id} | Get an item by ID | None | To-do item |
| POST /api/todo | Add a new item | To-do item | To-do item |
| PUT /api/todo/{id} | Update an existing item | To-do item | None |
| DELETE /api/todo/{id} | Delete an item | None | None |
The following diagram shows the basic design of the app.
-
The client is whatever consumes the web API (mobile app, browser, etc). We aren’t writing a client in this tutorial. We'll use Postman or curl to test the app.
-
A model is an object that represents the data in your application. In this case, the only model is a to-do item. Models are represented as C# classes, also know as Plain Old C# Object (POCOs).
-
A controller is an object that handles HTTP requests and creates the HTTP response. This app will have a single controller.
-
To keep the tutorial simple, the app doesn’t use a persistent database. Instead, it stores to-do items in an in-memory database.