start_index as a String in filing-history response

API Issues
#1

Hi,

If a start index parameter is given to the filing history url, the response contains a start_index that isn’t a number but a string. It’s easy to reproduce, as this happens right from the Try Out filing history page. I’m copy-pasting what I see there below:

Request
GET /company/00022705/filing-history?category=accounts&start_index=25 HTTP/1.1
Host: api.companieshouse.gov.ukundefined
Response status
200 OK
Response body
{
  "start_index": "25",
  "items_per_page": 25,
  "filing_history_status": "filing-history-available",
  "total_count": 34,
  "items": [
    ...
Is there a bug using start_index parameter?
#2

+1! E.g. via curl:

curl -u{MYAPIKEY}: "https://api.companieshouse.gov.uk/company/SC229764/filing-history?category=accounts&start_index=10"

{
    "items":
    [ ... ],
    "total_count":16, "filing_history_status":"filing-history-available",
    "items_per_page":25,
    "start_index":"10"
}

No start index parameter, you get an integer start_index (0).

Doesn’t seem to affect the other end-points which take a start_index e.g. search, search company, search officer, charges, officer appointment list, PSC list.