PART 2

PART 2

1. Calling the API

   • Authentication
     • No authentication is required to use the icanhazdadjoke.com API.
   • API response format
     • All API endpoints follow their respective browser URLs, but we adjust the response formatting to be more suited for an API based on the provided HTTP Accept header. Accepted Accept headers: text/html - HTML response (default response format) application/json - JSON response text/plain - Plain text response
   • Custom User Agent
     • If you intend on using the icanhazdadjoke.com API we kindly ask that you set a custom User-Agent header for all requests. Setting a custom User-Agent header for your code will help us be able to better monitor the usage of the API and identify potential bad actors.

2. Endpoints

   • Fetch a random dad joke
   • Fetch a random dad joke as a Slack message
   • Fetch a dad joke
   • Fetch a dad joke as an image
   • Search for dad jokes
   • GraphQL

3. Prescribed criteria

   • PC01
     • The application must display API data aesthetically.
   • PC02
     • The application must be efficient, modular and have accurate code.
   • PC03
     • The application must have an algorithm to retrieve, process and display the dad jokes data from the API.
   • PC04
     • The application must receive data in one format and programmatically transform it into another format for sharing/displaying.
   • PC05
     • The application must make use of a publicly available API listed in the technical proposal pdf.

4. Self Determined Criteria

   • SDC1
     • The API must have a button where they press the website logo which refreshes the page
   • SDC2
     • Be able to randomise the joke each time the click button is interacted with