Now that you've read these over-complicated explanations of REST (though they are the best ones we could find), this exercise will show you that it isn't so complicated.

In communicating with APIs, every piece of information is a resource. These are the nouns of your program.

There are only a few verbs that you can perform on these resources:

• GET
• POST
• PUT
• PATCH

Lets not worry about PUT and PATCH for the time being. There's nothing scary about them, we just won't need them at first.

We have worked with the Giphy API. For this API the nouns were GIFS. But there was more to it than that! As you recall, there were trending GIFS, GIFS by keyword, etc. We could GET these GIF objects, and that would return a JSON object with a bunch of information for us to do whatever we wanted with.

If we wanted trending GIFS, we went to one URL. If we wanted GIFS by a keyword, we went to another. The way that this is set up is the essence of REST.

Say we want to create our own RESTful API that for comedy video objects, much like our GIF objects.

We want urls that can return the following resources:

1. all videos in our database
2. an individual video based on the video ID
3. info on all comedians
4. info on a specific comedian based on comedian ID
5. all videos by a specific comedian
6. specific video by a specific comedian

In Express this will be done using JavaScript, but we will be PSEUDOCODING to remove the element of syntax from the equation so we can focus on REST itself. Here is pseudocode of routes for the above API:

// My pseudo-code routes:

GET ALL VIDEOS "/videos"

GET VIDEO BY ID "/vidoes/:id"

GET ALL COMEDIANS "/comedians"

GET COMEDIAN: "/comedians/:id"

GET ALL VIDEOS BY COMEDIAN "/comedians/:id/videos"

GET VIDEO BY COMEDIAN "/comedians/:id/videos/:id"

Note: In the above example any code preceded by a colon is a variable which would be filled in by specific information in the real requests. This is typical syntax in talking about variables in routes.

That's all there is to it!

Say we want to create an API similar to the one above, that returns data about icecream. We need to be able to get information about specific flavors, as well as all of the flavors we have in our database. We also want to get some flavors by category, like "fruity", "gluten free", or "chunky". Finally we want to add one POST route that allows users of our API to add new flavors!

Write Pseudocode like the above. Be creative, and follow RESTful conventions and best practices.

Fork and clone this repo. Submit your pseudocode in a markdown or text file by making a pull request on this repository.