From what we could find, this endpoint spec have changed, breaking our implementation of it.
We used to send any parameters as x-www-form-urlencoded and now it only accepts them as query string parameters.
I couldn’t find any mention of this breaking change, so can you please confirm if this was part of the changes deployed this morning?
@MArkWilliams tagging you for visibility as you’ve been able to provide some additional info in the past and escalate it internally. Appreciate any help/info.
(Reply to @glenn - not related to the original issue I think)
Ah - you may have run into the “trailing ‘/’ issue” here.
This has been working for me just fine, but it doesn’t work if I use your URL. However with a tiny modification it works. Your version (I’ve rearranged the curl command / get curl to calculate the header):
curl -u MY_API_KEY: 'https://api.companieshouse.gov.uk/search/companies/?q=test&items_per_page=50'
(Gives a 404 and no results)
curl -u MY_API_KEY: 'https://api.companieshouse.gov.uk/search/companies?q=test&items_per_page=50'
{"items":[{"kind":"searchresults#company",...
If you remove the trailing “/” after companies this should work, as in my example.