The CH JSON API sometimes uses camelCase, which is more common as JS itself generally uses camelCase. Eg: startIndex, startPage, totalResults
But sometimes the CH API uses under_scores: Eg: page_number, exceeded_max_results.
The API should use consistent casing.
The camel casing should only be on the company search responses, all other resources should use snake case. Company search currently uses camel case as we were trying to provide an OpenSearch compliant search endpoint. Since doing this it has become clear that this causes confusion as it’s inconsistent with the rest of the API. Company search is currently being worked on to bring it in line with the rest of the API.