Fix the dining API

[jbrower95]

(info in the email)

Hello,

I'm reaching out on behalf of Brown Dining. I received your name from CSI as the contact person for APPs that used our previous method of displaying dining menus. Our new website now has API coding to display menus and now displays menus for every location.

There are 2 options that can be used depending on which one works best for your particular app/feature/product.

Note that the “###” is the unique location ID for each of the units. Here are all the IDs for our campus dining locations:

1531 = Sharpe Refectory

1532 = Verney-Woolley

1533 = Andrews Commons

1534 = Blue Room

1535 = Josiah’s

1536 = Ivy Room

1537 = Campus Market

1538 = Café Carts

JSON API, version 1

http://legacy.cafebonappetit.com/api/1/cafe/###/date/2016-06-28/format/json

http://legacy.cafebonappetit.com/api/1/cafe/###/date/2016-06-28/days/5/format/json

JSON API, version 2

You use the following URL to get the unit's day parts and hours: http://legacy.cafebonappetit.com/api/2/cafes?cafe=###

Then, use the following URL to get the full menu for a particular date: http://legacy.cafebonappetit.com/api/2/menus?cafe=###&date=2016-06-28,2016-06-29

Then, use the following URL to get item details on a particular plate: http://legacy.cafebonappetit.com/api/2/items?item=######

Please let me know if you have any trouble with the code or if you have questions.

Warm regards,

[jpowell96]

Hi, So I'm trying to use the dining api based on this information. Instead of using the dining endpoints on the brown apis page, I should be using these endpoints now?

[hector-m]

I can't seem to actually get the menus from using your links. It basically just gives hours and icon information. Has anyone gotten it to work?