Fix getting an API error message
Mine were buried pretty deep.
Add test for deeply nested message parsing, too, with the exact message and structure I was getting.
Follow-up to !431 (merged) that apparently was not enough to solve what I was seeing.
Edited by Rylie Pavlik