/terrific-coot

http/web apis

Primary LanguageJavaScript

twitter api calls crud with https response examples

the code for the crud stuff

You will find the api calls to twitter and ibm watson in the first . it contains the api headers required.

The second/third is a crud application that uses express to enable different pages to be rendered per specs. there is also a file that has the different http headers listed with examples of their makeup and messages to fufill the other portion of these specs.

terrific-coot

Concept Focus: HTTP & Web APIs

Challenge Rating

<script src="https://gist.github.com/erikasf/4ab7d15edae0169cc1ae96ec66725f7c.js"></script>

This goal will likely be within your ZPD if you...

  • Can choose a goal that fits your ZPD
  • Have set up a web server with Node.js and Express
  • Are familiar with the concept of web servers and clients
  • Are comfortable jumping into a new codebase
  • Are interested in learning more about HTTP
  • Are interested in learning more about how the web works
  • Are interested in working with web APIs

Description

Explore the inner workings of HTTP, and apply your knowledge to interact with an external web API.

Concept focus goals like this one have some unique characteristics. If this is your first time working on one, read the Context for more information.

In working on this goal, you should explore concepts like:

  • The HTTP request-response cycle
  • HTTP verbs
  • URL components: host, path, query string
  • Routing web requests
  • Serving static resources
  • Interacting with an external web API

For guidance and support, start with the Resources provided.

Context

This goal is a concept focus goal, which means that it is not specific about the project you build, but rather the concepts that you apply in building it.

You will have to choose what to build. The details of the project are up to you. The project can be pre-written (so long as you have permission to use it) or a new one of your own choosing. You can even choose projects from other goals.

For inspiration, review the [list of project ideas][project-ideas].

The advantage of this is that you can work on whatever kind of project you like, so long as you focus on building your skills and knowledge of the concept in question.

The disadvantage is that it is very easy to get distracted or to waste time on non-essential tasks like making decisions about project design. It is also likely that you won't have as much support available, since other learners and coaches won't have worked on the same project as you. If you prefer to have more structure and deterministic outcomes, you may not enjoy this goal.

That being said, if you have the self-discipline, motivation, and resolve, you will likely benefit from choosing this goal.

An added benefit of working on a concept-focus goal is that you'll have a project with lots of great examples that you can reference later.

Specifications

  • [ x] Artifact produced is a GitHub repo.

  • [ x] GitHub repo contains a web server.

  • [ x] Can run the command npm start to start the web server at port 3000.

  • [ x] The web server source code is written using the Express library.

  • The web server handles routes for the following HTTP verbs

    • [x ] GET
    • [ x] POST
    • [ x] PUT/PATCH
    • [x ] DELETE

  • [ x] Examples of each HTTP verb usage are listed and linked to in the README

  • The web server makes use of the following response status codes

    • [x ] 200 (OK)
    • [x ] 201 (Created)
    • [x ] 400 (Bad Request)
    • [x ] 301 (Moved Permanently)
    • [x ] 403 (Forbidden)
    • [x ] 404 (Not Found)
    • [x ] 500 (Internal Server Error)

  • [ x] Examples of each status code usage are listed and linked to in the README

  • The web server uses URL components in routing and responding

    • [ x] Different paths trigger different routes
    • [ x] Values from the URL query string are used in a route

  • [x ] Examples of routing and query string usage are listed and linked to in the README https://github.com/erikasf/crudAPI

  • The web server makes use of the following request headers

    • [ ]x Accept
    • [ x] Content Type
    • [x ] Cookie

  • [ x] Examples of each request header usage are listed and linked to in the README

  • The web server makes use of the following response headers

    • Set-Cookie
    • Refresh

  • [x ] Examples of each response header usage are listed and linked to in the README

  • The web server serves different types of resources

    • [ x] Asset files (CSS, images)
    • [ x] Static HTML
    • [ x] Static JSON
    • [ x] Dynamic resources (content of response changes based on query params, request headers, and/or application state)

  • [ x] Examples of each response type are listed and linked to in the README

  • Example of a raw HTTP request and the server's raw HTTP response are included in the README

    • [ x] Examples show full HTTP message header
    • [x ] Examples show full HTTP message body

  • The web server makes the following request types to an external API

    • [ x] Get a resource
    • [x ] Create a resource
    • [x ] Update a resource
    • [ x] Delete a resource

  • [ x] Examples of each request type to the external API are listed and linked to in the README

  • [ x] The best resources you find for learning testing are added to a file resources.md

  • [ x] The artifact produced is properly licensed, preferably with the MIT license

Stretch

  • Web server is written using only the core Node.js modules (instead of Express, use the built-in HTTP module)
  • The web server makes use of the following request headers
    • Origin
    • Authorization
  • The web server makes use of the following response headers
    • Location
    • Access-Control-Allow-Origin
    • Content-Length
  • Web server uses OAuth to authenticate with the external API
  • OAuth routes are listed and linked to in the README
  • The web server exposes a JSON API at /api
    • API supports all CRUD actions for a resource (Create, Read, Update, Delete)
    • API follows a the RESTful design convention
    • API doesn't use database persistence (an in-memory store is fine)
  • Basic documentation for the API and each route is included in the README

Resources

Courses, Tutorials, Articles

Tools

  • Postman is a nice GUI for building HTTP requests
  • curl is a super useful tool for making HTTP requests from the command line

[project-ideas]: {{ site.url }}{% link project-ideas.md %}