Tech roles beyond coding

Stage 2 · Lesson 5 of 10

Reading JSON and API responses

Technical literacy

is the text format that most , configuration files and event logs use. An object sits inside curly braces and holds "key": value pairs, such as "name": "Sara". An is a list inside square brackets.

A value can be text in quotes, a number, true, false, null (meaning empty), or another object or array. Reading JSON comfortably lets you check what an API really returns. It also helps you spot a missing field in a bug report, write accurate docs and build .

Practise by calling a public API in or your browser. Then describe the response in words: what each field means, which fields are optional and which could be null.

Common trapassuming a field is always present because it appeared in one example. Real data has gaps, and good docs and specs say so.

A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock

Resources for this stage

Start with· follow one of these

  • VideoFree
    Crash Course Computer Science

    CrashCourse · Beginner

    Short free videos on how computers, networks and software work, pitched at beginners

  • CourseFree
    Select Star SQL

    Zi Chong Kao · Beginner

    A free interactive SQL tutorial on real data, enough for product and docs analytics

Practise

Keep handy

  • Clear reference for HTTP methods, headers and status codes

  • See how an API is described formally, which all three roles meet at work

Also worth your time

Mark this stage as not done?