csv api query returns 404 error

[charlieeatonphd]

When you change an API query from .json such as:

https://api.data.gov/ed/collegescorecard/v1/schools.json?school.degrees_awarded.predominant=2,3&fields=id,school.name,2013.student.size&api_key=***

to .csv, such as:

https://api.data.gov/ed/collegescorecard/v1/schools.csv?school.degrees_awarded.predominant=2,3&fields=id,school.name,2013.student.size&api_key=***

you get the following error:

Oops! An Error Occurred

The server returned a "404 Not Found".

Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.

[brownpl]

Thanks for reporting. I'll check into it and hopefully have a fix for it later this week.

[brownpl]

I've added a csv option. It is currently posted to our beta endpoint - is that something you could use for testing? I am waiting to see if any other issues come in that I can batch with this update, and aim to update production this weekend.

The beta endpoint is https://api.data.gov/ed/collegescorecard/beta/v1/schools - your existing keys should work fine.

[charlieeatonphd]

I can try that later today. You all had a CSV option that worked until Sunday April 4. Something done on Sunday broke it. Best, Charlie [image: photo] *Charlie Eaton (he/him)* Assistant Professor of Sociology, UC Merced Affiliated Faculty, UC Berkeley Center for Studies in Higher Education web: faculty.ucmerced.edu/ceaton2/ <https://twitter.com/charlieeatonphd> <https://www.facebook.com/eaton.charlie>

…

On Wed, Apr 7, 2021 at 1:54 PM Patrick Brown ***@***.***> wrote: I've added a csv option. It is currently posted to our beta endpoint - is that something you could use for testing? I am waiting to see if any other issues come in that I can batch with this update, and aim to update production this weekend. The beta endpoint is https://api.data.gov/ed/collegescorecard/beta/v1/schools - your existing keys should work fine. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1846 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQAYK3CAMO6VXAYROM2VO3THTBBHANCNFSM42P2E72Q> .

[brownpl]

Yes, there was a big API update on Sunday. The details are in the change log.

[brownpl]

The .csv functionality should now be available for you on the main endpoint.

[charlieeatonphd]

Thx! Best, Charlie [image: photo] *Charlie Eaton (he/him)* Assistant Professor of Sociology, UC Merced Affiliated Faculty, UC Berkeley Center for Studies in Higher Education web: faculty.ucmerced.edu/ceaton2/ <https://twitter.com/charlieeatonphd> <https://www.facebook.com/eaton.charlie>

…

On Fri, Apr 9, 2021 at 11:24 AM Patrick Brown ***@***.***> wrote: The .csv functionality should now be available for you on the main endpoint. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1846 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQAYK4TXOJW3O6DYDCVPI3TH5A7LANCNFSM42P2E72Q> .

[charlieeatonphd]

Hi. This still doesn't work. Neither https://api.data.gov/ed/collegescorecard/beta/v1/schools.csv?&fields=id,school.name,2016.repayment.repayment_cohort.3_year_declining_balance,2016.repayment.3_yr_repayment_suppressed.overall,2016.repayment.3_yr_repayment.overall&_per_page=100&_page=0&api_key=[MYKEY] nor https://api.data.gov/ed/collegescorecard/v1/schools.csv?&fields=id,school.name,2016.repayment.repayment_cohort.3_year_declining_balance,2016.repayment.3_yr_repayment_suppressed.overall,2016.repayment.3_yr_repayment.overall&_per_page=100&_page=0&api_key=[MYKEY] Please advise. On Tue, Apr 13, 2021 at 1:41 PM Charlie Eaton ***@***.***> wrote:

…

Thx! Best, Charlie [image: photo] *Charlie Eaton (he/him)* Assistant Professor of Sociology, UC Merced Affiliated Faculty, UC Berkeley Center for Studies in Higher Education web: faculty.ucmerced.edu/ceaton2/ <https://twitter.com/charlieeatonphd> <https://www.facebook.com/eaton.charlie> On Fri, Apr 9, 2021 at 11:24 AM Patrick Brown ***@***.***> wrote: > The .csv functionality should now be available for you on the main > endpoint. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#1846 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABQAYK4TXOJW3O6DYDCVPI3TH5A7LANCNFSM42P2E72Q> > . >

[brownpl]

A few initial thoughts. The first one is no longer available, our beta endpoint has been removed and all the functionality that was previously there should be available on production (the second link).

I just ran a few tests with your second one - for some reason, I am getting an invalid response in Chrome, but if I run it in Safari (I'm on a mac) I am getting a CSV download. Are you accessing this via the browser or by some other method? If it is the browser, a quick stopgap solution could be to try a different one. In the meantime, I'll see what I can figure out around why Chrome is having issues, and do a pass over others to ensure they are working as expected, and I'll respond here when I sort it out.

[brownpl]

After the data update last week, the export is appearing to work now as expected. I am not able to replicate the same issues with the invalid response. Please give it a shot and let me know if it remains an issue for you.