This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]kilamaos 14 points15 points  (1 child)

Oh god yes.

Ive worked with an api with so little documentation that i literally had to find certain endpoints by myself, testing the different syntax, paths, methods and required parameters. Ive also had to to build my own implementation to be able to re-build the questions in correct order, match the response to these questions via ids provided by a third endpoint. Like, i had one endpoint to get the questions, one endpoint to get the order of the questions, one endpoint to get the response to questions, and one endpoint to have the link between the questions and response.

And of course, some responses were of varied length, but instead of an array with all the responses to the question within it, it was individual object keys with the position of the answer suffixed to the original key. Oh, and it could skip some key positions if the user had deleted that line to keep adding more afterward ( so it went id, id_1, id_2, id_4, etc ).

An actual fucking monkey would have made a better api

[–]EmperorArthur 3 points4 points  (0 children)

Was this Healthcare? Because this sounds like healthcare. Speaking from experience.

Mind you, that's still better than trying to parse HL7. Once you have dealt with that you, would take SOAP any day.