← Back to problems

42. Task Tracker API

EASY
AuthenticationSecuritySystem Design

Design a pure REST contract for a task-tracking service - no diagram, no schema, just the API surface.

Design the REST API for a task-tracking service used by a small team. Users need to create tasks, fetch a single task, update its status/details, and delete it. There is no architecture diagram or database schema required for this problem - focus entirely on the API contract: routes, methods, authentication, and idempotency.
Log in to submit a solution

Comments

Log into join the discussion.