Web API Round - Design and Implement a REST Endpoint Layer

Question

## Problem

You are asked to design a REST API layer for a task management service. Implement the following endpoints (you may use any framework or pseudocode):

```
POST   /tasks              Create a task {title, description, due_date, assignee_id}
GET    /tasks/:id          Get task by ID
PATCH  /tasks/:id          Update fields (partial update)
DELETE /tasks/:id          Soft-delete a task
GET    /tasks?status=&assignee= List with optional filters + pagination
```

**Expected Request/Response:**
```
POST /tasks
Body:    {"title": "Fix bug", "due_date": "2025-04-30", "assignee_id": "u42"}
Response 201: {"id": "t123", "title": "Fix bug", "status": "open", ...}

GET /tasks?status=open&page=2&limit=20
Response 200: {"items": [...], "total": 87, "page": 2, "limit": 20}
```

## Follow-ups

1. How do you validate request bodies and return structured 422 errors?
2. Where and how would you add authentication/authorization (e.g., only assignee can update)?
3. How do you version the API when you need to introduce breaking changes?
4. Describe how you would rate-limit the list endpoint per client.

Web API Round - Design and Implement a REST Endpoint Layer

Question Details

Full Details

Topics

More from Rippling