Clarification on /data_objects API route

Development API
1

Seems that the data objects route is completely gone. Is that true? Seems its in the docs https://eol.org/docs/what-is-eol/data-services/classic-apis but I can’t get any API requests on that route to work. Maybe add some examples if the route is operational

2

The ID numbers of data objects have changes, but the API does work. See e.g. https://eol.org/api/data_objects/1.0/7561533.json

3

my bad, I guess the IDs I had in my docs were all just old ones that no longer exist.

4

@hammockj @BobCorrigan curious if the error behavior on this route is as desired.

e.g., if you do https://eol.org/api/data_objects/1.0/asdfafd.json

you get a 500 server error - whereas I’d expect a 400 series error - even though ID is part of the URL route instead of a query parameter, i’d still expect a 400 series error as routes that aren’t found on APIs usually are 400 series errors in my experience at least

e.g.,

curl -v http://api.crossref.org/worksss
> GET /worksss HTTP/1.1
> Host: api.crossref.org
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Content-Type: application/json
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Headers: X-Requested-With
< Content-Length: 105
< Server: http-kit
< Date: Wed, 28 Nov 2018 17:40:58 GMT
< X-Rate-Limit-Limit: 50
< X-Rate-Limit-Interval: 1s
< Connection: close
{"status":"error","message-type":"route-not-found","message-version":"1.0.0","message":"Route not found"}
5

I agree that a 400 series error is what you should expect here