API Refactor Design

[yifeili98]

Please use this issue for refactoring the API structure

let url=https://fhda-api-test.azurewebsites.net
Currently, we have the following APIs:
$url/course: get single course dict using quarter+crn
$url/course_list: get a list of all courses using quarter (optionally with a specific department)
$url/department: get a list of courses in a department using quarter+department (a bit similar to the one above)
$url/department_list get a list of department names using quarter
$url/seat: get enrollment details using quarter+crn
$url/seat_list get list of enrollment details of all courses using quarter

All above APIs are restful GET APIs, and we still need to implement more APIs for user, instructor, agreement, equivalency, user_story, etc...

Please try to share your ideas and we can build some successful APIs to use for this application : )

[yifeili98]

@VVVENIIDIICI Did a great job constructing the user stroy apis, so Imma open a google sheet to do something similar to other apis here

[hk-mp5a3]

Thanks for create a google sheet for APIs, Yifei.

I just add different tabs for different service. Please feel free to add your APIs to the corresponding tab.