Yep, i've seen stuff like this a lot, it's usually when the API has been written by people who don't quite get what xml is for. Especially the whole csv data inside an xml node, way too common for my liking, it's funny too because you wonder what the guy was thinking when he wrote it

"Gee i wish there were someway i could store this list of values in xml....hmmmmmm...i know csv!!!"

Yep, i've seen stuff like this a lot, it's usually when the API has been written by people who don't quite get what xml is for. Especially the whole csv data inside an xml node, way too common for my liking, it's funny too because you wonder what the guy was thinking when he wrote it

"Gee i wish there were someway i could store this list of values in xml....hmmmmmm...i know csv!!!"

I mean, I could overlook the fact that pracitcally every value is in a <DATA> node. And I could even overlook the fact that the descriptor for what that node actually contains is, for no good reason, specified in either the "id" or "type" attribute. But why oh why couldn't they have at least made the format of the data in the node consistent?

Also, did I mention that the backend of the API is (apparently) PHP with minimal error checking? If you send it bad data it usually responds with a blank document.