Problem in the readme api definition

[lewinernst]

When implementing the api i first created my jsons based on the structure in the readme, but had some problems after because i ended up with a non-conforming structure.
Based on the readme, I assumed the API would expect a PersonalData object with surname, given name, birth date and language and a ConfigurationData object with the otp.
Checking the api-definition in code however revealed that the structure is different: All of these are included directly on the top-level of the payload except for the names which are included as two parts of a name object.
Perhaps a hint could be included that the Headings don't correspond to objects?