Goodreads Developers discussion
bugs
>
Update book reviews API wrong
date
newest »
newest »
Yikes! Those are the best API doc's we've got. Not sure why that first route isn't working!
I'll get someone to fix this promptly.
Grunthos, the API docs were incorrect. The second URL you listed is the correct one. We'll update the docs soon. Thanks for pointing this out!
No problem; thanks for making the API in the first place.I take it from your response that you can't dump the API for verification purposes? It does not need to be pretty.
No problem; thanks for making the API in the first place.I take it from your response that you can't dump the API for verification purposes? It does not need to be pretty.
Not sure exactly what you mean. You want a sample response?
Oh, sorry, no...I meant if there were any way to dump the API definitions (eg. source/header/whatever) so that any future mismatches can be caught more easily, if that makes sense.
I suspect that what Grunthos is asking is if the API's have something like a WSDL that can generally be automatically generated from SOAP implementations, not that this is a SOAP implementation, but is there some equivalent.I would be interested in something like that too, but in addition it would be nice to have some documentation of what XML structure will be returned other than the one sample.
We don't really have that unfortuanately. All of our api routing i intermingled with out non api routing. The docs are really the best resource we have (thats what goodreads developers are referencing when we use the api).
It is listed as:
http://www.goodreads.com/review/show/...
(which just seems to return the review)....whereas:
http://www.goodreads.com/review/1212?...
does what is expected.
Any chance someone could do a quick & dirty dump of the current APIs for comparison in case of future mismatches?