# Inconsistent casing

**URL:** <http://forum.companieshouse.gov.uk/t/inconsistent-casing/55>\
**Category:** API Issues\
**Created:** [April 7, 2015, 11:43am UTC](http://forum.companieshouse.gov.uk/t/inconsistent-casing/55 "2015-04-07T11:43:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mike](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/m/58f4c7/32.png) [@mike](http://forum.companieshouse.gov.uk/u/mike)\
**Post date:** [April 7, 2015, 11:43am UTC](http://forum.companieshouse.gov.uk/t/inconsistent-casing/55/1 "2015-04-07T11:43:05Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![amaddaford](http://forum.companieshouse.gov.uk/user_avatar/forum.companieshouse.gov.uk/amaddaford/32/45_2.png) [@amaddaford](http://forum.companieshouse.gov.uk/u/amaddaford)\
**Post date:** [April 7, 2015, 2:42pm UTC](http://forum.companieshouse.gov.uk/t/inconsistent-casing/55/2 "2015-04-07T14:42:28Z")

</div>

The camel casing should only be on the company search responses, all other resources should use [snake case](http://en.wikipedia.org/wiki/Snake_case "Snake case"). Company search currently uses camel case as we were trying to provide an [OpenSearch](http://www.opensearch.org/Specifications/OpenSearch/1.1 "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.