Backend Study Lab · Games
← All games

API Route Builder

Design REST-style methods and routes for product requirements such as creating users, updating email, searching products, and nested comments.

Concept
REST API route design
Difficulty
Beginner
Play time
6-9 minutes
Path
Foundations

Interactive scenario

Playable game area: Make the next backend decision

Use the controls below. Feedback appears immediately and final scores stay in this browser.

Concept notes

Why this decision matters

API Route Builder is focused practice for REST API route design. It explains why each answer is safe, risky, or production-ready.

Backend APIs become easier to learn and maintain when their routes describe resources cleanly. This game turns common product requirements into method and route choices.

Learning objectives

  • Choose HTTP methods based on intent and idempotency.
  • Model resources with nouns, route parameters, and nested relationships.
  • Avoid action-heavy routes when a resource-oriented design is clearer.

How to play

  1. Read the backend product requirement.
  2. Pick the HTTP method and route that best model the resource change or read.
  3. Submit your design to see the explanation and move forward.

Scoring

  • A correct method and correct route earns full points.
  • A correct method with the wrong route earns partial learning feedback but no full score.
  • Final score rewards consistency across the full route set.

Backend concept notes

REST route design is about making resources and state changes predictable. Clients should understand the shape of the API without memorizing many custom verbs.

Routes are not only syntax. They encode ownership, scope, cacheability, and the difference between replacing a resource and partially changing it.

Common mistakes

  • Using GET for state-changing operations.
  • Putting verbs everywhere, such as POST /createUser, when POST /users is clearer.
  • Forgetting nested ownership, such as comments that belong to a post.

Review misses from this game

Keep practicing nearby backend concepts while the mental model is fresh.

APIs Beginner

HTTP Status Defender

Choose the correct HTTP status code for realistic backend scenarios and learn the response semantics behind each answer.

Time
5-8 minutes
Concept
HTTP status codes and response semantics
  • Foundations
  • HTTP
  • REST
  • status codes
Play HTTP Status Defender
Queues Intermediate

Message Queue Simulator

Tune workers, retries, and dead-letter behavior while jobs move through an async queue with failures and poison messages.

Time
7-11 minutes
Concept
Async jobs, retries, visibility timeout, and dead-letter queues
  • Production Reliability
  • Async Workflows
  • queues
  • retries
  • dead-letter queue
Play Message Queue Simulator

FAQ

Short answers for how this game fits backend interview and study practice.

Are action routes always wrong?

No. Some domain actions are clearer as action subresources, such as POST /orders/:id/cancellation. The key is to be intentional.

Should search use GET or POST?

Simple queryable searches usually fit GET with query parameters. Very complex searches can use POST to a search resource.

Leaderboard

Top 10 scores for the current ruleset. No account required.

Loading leaderboard...

    Finish the game to load your latest local score.