Turns out we might need that route for getting the job information (date, recurring, etc) to populate the tableView of jobs. Right now, if a user creates a job, I have access to that information and can populate a tableView with it. However, if the user loads the application with their token, I can use GET /userInfo to get an Array of the job ids, but can't get the actual job information (date, recurring, etc) to populate the tableView.
It would be nice to have a tableView too see the job information that was saved on the sever, but this wouldn't be needed at all for the demo tomorrow.