"total_results: null" in OfficersList

When listing the officers for company 10271424, the response is:

{
  "kind": "officer-list",
  "start_index": 0,
  "total_results": null,
  "active_count": null,
  "etag": "9dca6913c2eda42c1104d078e8af15eccd3f0afc",
  "items_per_page": 35,
  "items": [
    {
      "address": {
        "address_line_2": "Grappenhall",
        "country": "United Kingdom",
        "postal_code": "WA4 2LA",
        "locality": "Warrington",
        "premises": "9",
        "address_line_1": "Heathfield Park"
      },
      "appointed_on": "2016-07-11",
      "nationality": "British",
      "officer_role": "director",
      "name": "AULT, John, Dr",
      "occupation": "Director",
      "country_of_residence": "United Kingdom",
      "links": {
        "officer": {
          "appointments": "/officers/2L_Ppw33TOVN-cyWM9lvUl6hiSw/appointments"
        }
      },
      "date_of_birth": {
        "year": 1970,
        "month": 8
      }
    }
  ],
  "resigned_count": null,
  "links": {
    "self": "/company/10271424/officers"
  }
}

The schema specifies total_results to be an (optional) integer. My question is whether or not total_results being set to null is a valid API response or a bug. If it is a valid response, will there ever be more than one page of officer results?

Many thanks,

Bruce

The same issue occurs with company numbers 10271422 and 10271423. It may be worth noting that this issue only occurs with companies who only have a single officer.

@GoCardless

This is a bug and we should be returning an integer for total_results. Thanks for bringing this to our attention and we will look to resolve as soon as possible.

Thanks,

@mfairhurst