Check out an API response
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- api, documentation
Research direction
Open Chrome DevTools' Network tab and request http://api.tvmaze.com/shows/82/episodes. Inspect the request and response fields listed in the issue, then share the six answers with the other learners on Slack; completion means all questions have been answered.
Written by the indexing model from the issue text.
Description
Learning Objectives
- Extract important information from an HTTP response
Why are we doing this?
This task will get you to really think about the response you get back from an API. Use Chrome Dev Tools to examine the response you get back from the server.
Look at a request in Chrome Dev Tools
In Google Chrome, open dev tools network tab and enter this URL into the browser: http://api.tvmaze.com/shows/82/episodes
Answer the following questions:
- What's the status code the server sent back?
- What HTTP method did the browser use to make the request?
- What is the request path?
- What is the first line of the response body?
- What is the value of the response header called "Content-Type" ?
- What is the value of the request header called "User-Agent"
Maximum time in hours
.5
How to submit
Share your answers with the other learners on Slack.
Did you get different answers to other people? Ask them how they worked them out!
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 276
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeYourFuture/Module-Data-Flows
-
🏕 Priority Mandatory 📅 Sprint 3 Core Module-Data-Flows Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 Core Module-Data-Flows Submit:None
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 3 Core Module-Data-Flows Submit:None
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 2 Core Module-Data-Flows Submit:None
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 1 Core Module-Data-Flows Submit:None
Difficulty 1/5 1-3 hours Newbie friendliness 35/100
All issues in CodeYourFuture/Module-Data-Flows
Similar issues
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AllTheMods/ATM-10-L#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SignalK/n2k-signalk#345 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
JuliaPluto/PlutoPlotly.jl#72 ·