Skip to main content

Sep 16, 2020 - 1 minute read - API Testing API Challenges Evil Tester

How To - GET todo 404

This post and video shows how to complete the challenge GET /todo 404 using Insomnia.

What are the API Challenges?

Our API Challenges Application has a fully functional cloud hosted API, and a set of challenges to work through.

GET /todo (404)

Issue a GET request on the /todo end point should 404 because nouns should be plural

  • This will show you an error status code 404
  • 404 means ‘not found’ i.e. we tried to access something that does not exist
  • REST API Endpoints are usually plural e.g. /todos we would not normally expect an API to respond to both /todos and /todo

Basic Instructions

  • Issue a GET request to end point “/todo”
    • if running locally that would be
      • http://localhost:4567/todo
    • if running in the cloud that would be
      • https://apichallenges.herokuapp.com/todo
  • The request should have an X-CHALLENGER header
  • The response status code should be 404

Insomnia Details

> GET /todo HTTP/1.1
> Host: apichallenges.herokuapp.com
> User-Agent: insomnia/2020.3.3
> X-CHALLENGER: x-challenger-guid
> Accept: */*
< HTTP/1.1 404 Not Found
< Connection: close
< Date: Thu, 27 Aug 2020 13:46:19 GMT
< X-Challenger: x-challenger-guid
< Content-Type: text/html;charset=utf-8
< Server: Jetty(9.4.z-SNAPSHOT)
< Via: 1.1 vegur

Overview Video

Watch on YouTube

Patreon ad free version

Learn More and Start Testing


You will need a Github account to comment. Or you can contact me with your comment.

I reserve the right to delete spam comments e.g. if your comment adds no value and its purpose is simply to create a backlink to another site offering training, or courses, etc.