Parse structured values without guessing types
See this course’s project requirements
A tested local API-response viewer with a request contract, validation rules, six response cases and an honest integration handoff.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Request/response contract with limits.
- Type and status observations.
- Working local viewer.
- Explicit empty/error/validation behavior.
- Six-case test matrix and README.
Review and revise
Use these criteria to check your work and choose what to improve.
- Fields and types are understood.
- Failures do not show stale results.
- All six cases behave as described.
- Simulation and live-integration limits are explicit.
Want more background?
The idea in everyday life
Build a read-only viewer for a fictional library-hours API contract.
Parsing turns text into values; it does not decide whether the values are suitable.
Parse structured values without guessing types — guided practice
Distinguish JSON strings, numbers, arrays and missing fields.
Save api-viewer.html from the download and open it in a modern browser. Open its source in a text editor. The complete original file supplies every fixture and function. It simulates GET /hours locally; it does not contact a real library. Reload after edits; restore the supplied file before each lesson unless told otherwise.
1. Inspect a number
Find opens:12 in the success East record. In JSON text it is written "opens":12.
You should see: The value is numeric.
Number operations require a deliberate type choice.
2. Inspect the wrong type
Choose wrong-type and click Load hours.
You should see: The viewer reports Invalid branch record.
The string "12" is not the integer 12 in this contract.
3. Run a parser example
In the browser console run the exact expression.
typeof JSON.parse('{"opens":12}').opensYou should see: The returned value is number.
typeof reveals the parsed value’s JavaScript type.
4. Compare a missing value
Run the second expression.
JSON.parse('{"name":"West"}').opensYou should see: It returns undefined because the field is absent.
Missing is different from an explicit zero.
What to finish
A three-case type note: number, string and absent.
Watch for this
Automatically converting every blank or absent field into zero.
How can I tell I understand it?
Complete the changed case, explain your result, and pass the three application checks.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkOptional course overview video · same video as Lesson 1
APIs for Beginners - How to use an API (Full Course / Tutorial)
From freeCodeCamp.org. Watch here or open it on YouTube .
Optional course overview. Follow the written steps below at your own pace.Tools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-12
Opened and inspected on 2026-09-12: JSON types and parsing.
Access: Free public web page; no paid enrollment required.
Reuse: Public reference; link only. LifeStarter prose, exercises and files are independently authored.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.