Insolvency API issue companies house

Hi,
We are not getting valid response from Insolvency API.
Could any one help me out.

cheers

Hi,
Streaming API’s do not have a response in that sense, they have a stream (it’s in the name!).
The insolvency endpoint compared to say the filling and / or companies endpoint, is ‘quiet’ and does not always have data to stream. You’ll have to connect and wait for data to be available, in the meantime, you’ll still get the ping to know that you are connected.

It is not Streaming API. Regular HTTP get request. We get valid response for GET https://api.company-information.service.gov.uk/company/{companyNumber}/registered-office-address
with the same authentication header.

we have issues in response , status is ok. response body is corrupt?
GET https://api.company-information.service.gov.uk/company/{company_number}/insolvency

If you get an OK response plus a (corrupted) body, what headers are you sending AND what headers are you receiving? Could the body be zipped?

https://developer-specs.company-information.service.gov.uk/companies-house-public-data-api/reference/insolvency/get

only basic authentication headers

We tried this
[https://api.company-information.service.gov.uk/company/{companyNumber}/registered-office-address]
this works with the same authentication.

This used to work, and we have no code change from our side. We want to know anything has changed in the API side.

We’re currently facing the issue described here. Getting a 200 OK response without a body (content-length is 0). Was working fine before and no code changes were done.

Thanks Tiago, how to escalate this? I sent email, but no response yet.

Thank you all for taking the time to report this. We are aware of this and are investigating.

Mark,
Could you please give an update on this.

Thanks
Amala

There was a change made on 28th July that has resulted in a change to the responses. This is still being investigated.

Hi,

Not sure if this is related but we have started getting a “410 gone” response when calling the insolvency endpoint. The body contains a timestamp and a message of "Exception occurred while processing the API request with correlation ID: ".

Is this related to the changes mentioned ? Or is it something else ?

Many thanks,

Rob

Yes, all related to the same issue.

Is there any updates on this please?

We made a change last week that should have resolved the 410 return codes.