How to show data from an external API on your website
Use your own practice account and test data. Record an observation for each completion claim. You can print this worksheet or keep your answers in your own notes; this page does not submit them.
1. Open the ready lookup
Which repository did you look up, and what result did the running page actually display?
Review your work
Names the public owner/repository actually requested and the returned identity.
Reports the observed count/time or precise service failure without hardcoding an example value.
2. Check one successful response
Did the page result match the repository response you inspected?
Review your work
Matches the page’s identity and star count to the same public service response.
Does not present an error response or missing field as a normal zero-valued result.
3. Try missing and unavailable states
What did the two failure cases show, and could the visitor recover?
Review your work
Records distinct results for a missing repository and an assisted failed-request test.
Checks that the query remains usable for correction or retry without adding a private browser token.
4. Add a useful result
Add the open issues and pull requests total. How did its displayed value compare with the response, and what happened in the missing/unavailable tests?
Review your work
Displays open_issues_count as open issues and pull requests, not only bugs or issues.
Compares the new value with a response and repeats normal, missing and unavailable states.