Creating a REST API: Handling GET requests

April 05, 2018 0 Comments

Creating a REST API: Handling GET requests

 

 

After taking a brief detour to create a generic database module, it’s time to continue on with the development of the high-level components discussed in the parent post. In this post, you will add routing, controller, and database logic to handle an HTTP GET request on an “employees” API endpoint.

Adding routing logic

Express ships with a Router class that makes it easy to route HTTP requests to the appropriate controller logic. Route paths define the URL endpoints of the API and can contain route parameters that capture values in the URL (query strings are not part of route paths).

There are many ways you could define the routes for your application. For example, when the app starts, you could read all the files in the controllers directory and auto-generate routing logic based on some predefined rules, such as the filenames and properties they expose. Alternatively, you could add a file to the config directory and read that at start time. Consider such automation when your API matures and its patterns are well known.

In this application, you will take a slightly lower-level approach by defining routes programmatically via a new router module. Create a new file named router.js in the services directory. Add the following code to the file and save your changes.

The router module starts by bringing in Express and then creates a new instance of Express’ Router class. The router’s route method is used to get an instance of a single route based on the route path passed in. In this case, the path includes a parameter named id which is made optional by the question mark that follows it. The route that’s returned from route has methods which correspond to HTTP methods and allow handlers to be defined. In this case, the get method is used to map an incoming GET request to the get function defined in the employees controller (which will be created in the next part).

At this point, you have a router but it’s not currently used in the application. To use it, open the services/web-server.js file and remove the line at the top that requires the database module (that was only used for testing in the previous post). Add the following line of code in its place.

Next, use the following code to replace the entire app.get handler that responds to GET requests using the database module (all 7 lines).

Now the router is required into the web service module and “mounted” at /api. This means that full URL for the employees endpoint will be http://server:port/api/employees/:id.

Adding controller logic

The controller logic will take over from the point that the endpoint and HTTP method are known. Because the web server is built with Express, the controller logic will be defined with custom middleware, or functions that have access to the request and response objects, as well as the next function.

The middleware function will use the data coming in from the request object to generate a response which is sent with the response object. Because the controller function will attempt to end the HTTP request, the next function will only be invoked if an error occurs.

I usually create one module in the controllers directory for each endpoint in the API. Here are some examples:

URL Endpoint Controller File
/api/employees/:id controllers/employees.js
/api/departments/:id controllers/departments.js
/api/departments/:dept_id/employees/:emp_id controllers/departments_employees.js

Within each module, a middleware function that handles a particular HTTP method will be defined and exposed. I usually name each function based on the HTTP method it handles which makes it easy to wire things up in the router module.

Go to the controllers directory and open the employees.js file that was created in the first part of this series. Copy and paste the following code into the file and save your changes.

Here’s a line by line breakdown of the controller module so far:

  • Line 1: The employees database API (created in the next part) is required in.
  • Lines 3-23: An async function named get is declared. A try-catch block is used in the body of the function to catch exceptions thrown on the main thread and pass them to the next function.
    • Lines 5-7: A constant named context is declared – this is a generic object that will contain properties that are relevent to the database API’s find method. An id property is added to context based on the value that comes in via req.params.id.
    • Lines 9: The database API’s find method is used to fetch the appropriate employee records in the database.
    • Lines 11-19: Conditional logic is used to determine the correct HTTP status code and body for the response. If one employee was requested but not found, a “404 – Not Found” error code is sent as a response. Otherwise a “200 – OK” code, along with a JSON-based response body, is sent.


  • Line 25: The get function is exported from the module so it can be used in the router module.

The req.params object is just one several properties used to get data from the incoming request object. Other common properties include req.query for the query string values in the URL, req.body for the request body, and req.cookies. HTTP headers can be fetched using the req.get method.

If you don’t like the magic numbers used for the status codes, consider using a module like http-status instead. That module provides constants like OK and NOT_FOUND that can add clarity to the code.

Adding database logic

As I mentioned in the parent post, I’ll be using the Node.js database driver/API for Oracle Database, node-oracledb, instead of a higher level ORM (I’ll likely cover ORMs in the future). To start the employees database module, open the db_apis/employees.js file and add the following code.

The employees database module brings in the generic database module and initializes a constant named baseQuery to a SQL query on the employees table. Double-quoted column aliases are used to control the case of the keys returned.

Next, a function named find is declared and used to execute the query and return the rows fetched. If the context parameter passed in has a “truthy” id value, then a where clause is appended to the query so that only a single employee is returned.

Note that the value of context.id was not appended to the query directly. Instead, a placeholder named :employee_id was used instead – this is known as a bind variable. Using bind variables with Oracle Database is VERY important, for security and performance reasons. The value of the bind variable is assigned to the binds object which is passed to database.simpleExecute, along with the query.

Once the database module is in place you should be able to start the application and test. Once started, navigate Firefox to http://localhost:3000/api/employees. You should see a list of employees as follows (I’ve collapsed a couple):

You can fetch a single employee by adding an id to the end of the URL, for example: http://localhost:3000/api/employees/100.

At this point, your API can handle GET requests on the employees endpoint. In the next post, you will round out the CRUD functionality by adding logic that handles POST, PUT, and DELETE requests.


Tag cloud