Open API specification points to 127.0.0.1

[p.zajdler]

Hi,

I’m looking to generate models based on the Open API spec that (only theoretically) can be downloaded from the docs.

Unfortunately, upon inspecting the Open API spec file (https://developer-specs.company-information.service.gov.uk/api.ch.gov.uk-specifications/swagger-2.0/spec/streaming.json), I noticed that all references point to 127.0.0.1. I’m assuming that you can see the problem already.

It wouldn’t be too much of a problem, but there’s multiple levels of nested files, all pointing to 127.0.0.1 and no editor/viewer I’m aware of is able to resolve them.

That being said, may I ask that this is fixed to allow pulling the spec? If it’s easier for the time being, can I please ask for a single-file spec instead?

[voracityemail]

This has reported to Companies House before, the only response I can remember is that it wasn’t a priority. That was 2022.

CH Public Data API OpenAPI specification refs refer to localhost

Simply replace the highlighted with: developer-specs.company-information.service.gov.uk for every schema reference PS: you may have a different port number concatenated to the 127.0.0.1 [image]

Another example thread with homebrew fix suggestions:

Importing Streaming API Swagger Fails

I managed to get a complete API spec with correct references, by writing a little script that gets the entrypoint url and then resolves all JSON references, while I run a simple proxy server on localhost that redirects to developer-specs.company-information.service.gov.uk. I ended up with a single large API spec file. I know it sounds a bit ridiculous to do all this, but it worked for me. Unfortunately I found that the response formats in the API spec do not always match the actual response for…

[p.zajdler]

Hah, I was planning on writing such a script myself in case I didn’t receive an answer. Well, thanks for letting me know - I kind of assumed that this hasn’t been raised before - you know, someone would’ve fixed if by now if it has