Flatiron School Phase 1 Project

Nate McGraw
2 min readAug 11, 2021

The API that I picked is the Bored API, which is a REST API, the stated purpose of which can not be stated any more accurately than on their about page:

Due to the nature of the API, all data is presented in JSON format and all input has to be hand-typed, so any typo could cause an invalid request. For my project, I wanted to fix that by creating a GUI to help form the requests and present the data returned in a more human-readable format.

The user is initially presented with a search tab containing a form with inputs for all parameters for the API. The customer can either search for an activity based on specified criteria(such as number of people involved, cost, etc.) or they can search for a an activity by a unique identifying number. Once an activity is selected, it is displayed in a Key:Value format:

When the settings are unchanged, or the search by ID field is empty and that search is used, a random activity is returned. When invalid parameters are used or no results have been returned, an error message is presented:

view Activity

The favorites tab interacts with a json server running locally which stores the Name and ID of the activity which can be displayed in the search tab by selecting the desired activity and clicking View Activity, the activity can also be removed from the favorites list which will update the database as well as the list on the screen.

--

--

Nate McGraw

Software Engineering student at Flatiron School by night, Help Desk Analyst by day