API routes and status codes

What this means

An API route combines an HTTP method and path, such as GET /tracks or POST /quiz-attempts. Status codes summarize the result.

In beginner terms, this topic answers one practical question: "What should I write, and why does React care about it?" Do not try to memorize the syntax first. First understand the idea, then connect the syntax to that idea.

Why it matters

Clear routes and correct status codes help clients understand success, validation errors, missing records, and server failures.

When you build real React screens, this idea helps you decide where data should live, what the user should see, and what should happen after an interaction. That is why this lesson is part of the main path instead of being an optional detail.

Step by step

1. Notice the UI problem this topic solves. 2. Look at the smallest possible example. 3. Change one value and predict what should appear. 4. Run the example and compare the result with your prediction. 5. Use the practice task before moving on.

Small example

GET /tracks -> 200
POST /tracks with invalid data -> 400

Common mistake

Do not return 200 OK for every failure. Use meaningful status codes and error bodies.

Practice task

Design GET, POST, PATCH, and DELETE routes for lessons.

Remember this

Methods describe intent; status codes describe results.