In order to keep track of what we started to discuss in today's meeting I open this issue:

Due to the last decisions that were made in commonalities (based on votes (camaraproject/WorkingGroups#169) related to this issue(camaraproject/WorkingGroups#157)) the current guideline indicates that the API input and output business data would follow the lowerCamelCase notation

Currently there are two flavors in Number Verification and Sim Swap APIs. The argument to include MC proposal was to have a solution that is consistent with the available solution in the market AS-IS. But now, we have to align it to the guidelines so it’s not going to be the AS-IS definition. Mobile Connect APIs (proposed in SIM Swap and Number Verification Sub-Projects) parameters follow snake_case notation and now must be changed to lowerCamelCase.

Maybe it’s the time to reevaluate this part and see what benefits developers can get from having APIs similar to MC but not exactly aligned with them nor with 3GPP/TMF?