# Open API specification points to 127.0.0.1

**URL:** <http://forum.companieshouse.gov.uk/t/open-api-specification-points-to-127-0-0-1/8157>\
**Category:** Documentation Issues\
**Created:** [July 7, 2024, 10:12am UTC](http://forum.companieshouse.gov.uk/t/open-api-specification-points-to-127-0-0-1/8157 "2024-07-07T10:12:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![p.zajdler](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/p/a3d4f5/32.png) [@p.zajdler](http://forum.companieshouse.gov.uk/u/p.zajdler)\
**Post date:** [July 7, 2024, 10:12am UTC](http://forum.companieshouse.gov.uk/t/open-api-specification-points-to-127-0-0-1/8157/1 "2024-07-07T10:12:02Z")

</div>

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](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?

---

<div class="post-metadata">

**Author:** ![voracityemail](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/v/b77776/32.png) [@voracityemail](http://forum.companieshouse.gov.uk/u/voracityemail)\
**Post date:** [July 7, 2024, 6:07pm UTC](http://forum.companieshouse.gov.uk/t/open-api-specification-points-to-127-0-0-1/8157/2 "2024-07-07T18:07:06Z")

</div>

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

[https://forum.aws.chdev.org/t/ch-public-data-api-openapi-specification-refs-refer-to-localhost/4253/5](https://forum.aws.chdev.org/t/ch-public-data-api-openapi-specification-refs-refer-to-localhost/4253/5)

Another example thread with homebrew fix suggestions:  
[https://forum.aws.chdev.org/t/importing-streaming-api-swagger-fails/4828/16](https://forum.aws.chdev.org/t/importing-streaming-api-swagger-fails/4828/16)

---

<div class="post-metadata">

**Author:** ![p.zajdler](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/p/a3d4f5/32.png) [@p.zajdler](http://forum.companieshouse.gov.uk/u/p.zajdler)\
**Post date:** [July 8, 2024, 6:55am UTC](http://forum.companieshouse.gov.uk/t/open-api-specification-points-to-127-0-0-1/8157/3 "2024-07-08T06:55:30Z")

</div>

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 😅
