Clarification on /data_objects API route


Seems that the data objects route is completely gone. Is that true? Seems its in the docs but I can’t get any API requests on that route to work. Maybe add some examples if the route is operational


The ID numbers of data objects have changes, but the API does work. See e.g.


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


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

e.g., if you do

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


curl -v
> GET /worksss HTTP/1.1
> Host:
> 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"}

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