HTTP 401 failure when querying the API for company officers

API Issues
#16

Seems like a false alarm from me. Found bug on our side. Sorry :frowning:

#17

Yes, this is being looked into. We have an internal ticket system where this is now logged.

2 Likes
#18

Thank you @MArkWilliams!

Just as a FYI, this issue continues for us, the latest failure taking place at 2024-07-17 10:24:01,944 on our system, if that helps:

Failed to query [https://api.company-information.service.gov.uk/officers/uXM5cKq9ruGl1pNlvcoZ-zdvyfA/appointments?start_index=0&items_per_page=50]. HTTP Status [401]

Regards

#19

Hi @MArkWilliams, sorry for pestering however as I’m unable to view the status of the internal ticket, would you mind providing an update on the progress here please? This issue is affecting quite a few of our customers. Please also see below for another error today:

Failed to query [https://api.company-information.service.gov.uk/company/14939699/officers?start_index=0&items_per_page=50]. HTTP Status [401]

Regards

#20

Hi @MArkWilliams, has there been any updates on this issue please? We have further failures still coming through:

Failed to query [https://api.company-information.service.gov.uk/company/10639447/officers?start_index=0&items_per_page=50]. HTTP Status [401]

Regards

#21

Also getting CORS errors with persons with significant control endpoint.

fetch("https://api.companieshouse.gov.uk/company/10993724/persons-with-significant-control", {
  "headers": {
    "authorization": "Basic API_KEY",
  },
  "referrer": "https://b2bfinance.com/",
  "referrerPolicy": "strict-origin-when-cross-origin",
  "body": null,
  "method": "GET",
  "mode": "cors",
  "credentials": "include"
});

Curl works as expected.

#22

Please see Company Officers API 401 CORS Issue

#23

Still investigating sorry.
This is proving difficult to track down.

1 Like
#24

Hi @MArkWilliams,

Thanks for the last update. Are there any reportable updates on this issue today? Please don’t hesitate to let me know if you require any more information from our side to aid in your investigation.

Regards

#25

No, sorry, nothing reportable. The random nature is proving a problem.

#26

HI @MArkWilliams. I’m not sure if this is any help, but our feed appears to have stabilised over the last few days. I’ll keep monitoring, but others may still be experiencing issues.
image

#27

Actually, that is very helpful, thank you.
During investigations, we have been restarting parts of the service and that might account for the recent improvement. Investigations still on-going though.

#30

Hi @MArkWilliams, thanks for your continued investigation. Unfortunately, we’re still seeing errors our side, the latest happening @ 2024-07-29 10:36:05,042 BST:

Failed to query [https://api.company-information.service.gov.uk/company/13360403/filing-history?start_index=0&items_per_page=35]. HTTP Status [401]

Regards

#31

Hi @MArkWilliams We’ve also seeing this particular issue, but only when attempting to use this endpoint (Companies House Public Data API: Company profile) - the general search endpoint seems to work fine (Companies House Public Data API: Search companies)

We’re getting a 403 Forbidden error on the OPTIONS request and a CORS issue on the preflight (Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.).

This is happening when programmatically attempting to fetch data using Javascript. It was fine until recently (although I can’t say exactly the last time this worked, it’s been a while since we’ve attempted to use the direct company profile GET endpoint, mainly relying on the general search one).

#32

I believe the error, { error: ‘Invalid Authorization header’, type: ‘ch:service’ }, is happening because of the API key encoding. On the companies house dashboard the key is in hex format. When trying to use that key in axios call the url, https://api.companieshouse.gov.uk/search/companies?q=${searchTerm}, have been returning a response with status code 400, Bad request. Inside the response the returned data have the object, {error: ‘Invalid Authorization header’, type: ‘ch:service’ }.

So I have converted the API key to base64 and it start working. Using postman it is possible to get the base64. Use the authorization tab to add Basic Authorization, username - API key and password - blank. Send a get request, then go to Headers tab where you can get the Authorization in base64.

#33

Hi @MArkWilliams, has there been any update on this issue since the last review?

#34

Hi @MArkWilliams, do you have any update regarding the resolution of this issue please?

Regards

#35

Hi @MArkWilliams do we have an update on this?

#36

Hi @MArkWilliams, there have not been any updates regarding this issue for 25 days now. Can you please provide an update on this issue. Is this considered resolved on your side or are you still investigating?

Regards

#37

A fix has gone in for this CORS issue.
If you are making CORS requests you will need to ensure the api key that you are using has your site in the js_domains array.