Start_index field is sometimes returned as String instead of Int

[cos_marginean]

Paging through a result set is sometimes returning a String instead of Int for the start_index field. Besides being silly, this can break client code that relies on a cast to Int there.

This request produces an Int:

...
"start_index": 0,
...

This request produces a String:

...
"start_index": "50",
...

[voracityemail]

Agreed - and since start_index starts from zero looks like you’ve found the equivalent of a stack overflow…

I think there are still outstanding bugs in the opposite direction e.g. when items_per_page and start_index are very small - see this thread:

Is there a bug using start_index parameter?

Have you an example? This seems to be working as usual for me. There are a couple of things to note about start_index and search in general to watch for but it’s not clear what your issue is. I’m guessing the most likely one that you have is something like you have to use a multiple of number of items_per_page - e.g. if you alter start_index the “paging” mechanism seems to expect you to specify both that and items_per_page. I believe “start_index” starts from zero. It seems that one should …

If you wave at one of the Companies House folks (use “@” with one of their usernames) that might attract their attention faster - not sure?

Good luck