Intermediate Code Reading #API #JSON #REST #data-structures

📡 API Responses & Data Structures

2 exercises — read JSON API responses and choose the best plain-English description for different audiences: junior developers, product managers, and QA engineers.

0 / 2 completed

Describing API responses in English

Name the top-level structure: "This is a [success / error / paginated] response."
Explain field purpose, not just the name: not "id field" → "a unique identifier for the user"
Identify nested objects: "Inside 'preferences', there is an object that stores…"
Explain HTTP status codes in words: 200 = success, 422 = validation error, 404 = not found
Know your audience: engineers need technical detail; PMs need business meaning

1 / 2

A junior developer receives this JSON response from a REST API and asks what it represents. Which explanation is the most complete?

{
  "data": {
    "user": {
      "id": "u_48f2a",
      "name": "Olena Kovalenko",
      "email": "olena@example.com",
      "role": "admin",
      "createdAt": "2023-11-15T09:30:00Z",
      "preferences": {
        "theme": "dark",
        "language": "uk",
        "notifications": true
      }
    }
  },
  "meta": {
    "requestId": "req_9c21b",
    "duration": 41
  }
}