# Importing Streaming API Swagger Fails

**URL:** <http://forum.companieshouse.gov.uk/t/importing-streaming-api-swagger-fails/4828>\
**Category:** API Issues\
**Created:** [February 10, 2022, 12:54pm UTC](http://forum.companieshouse.gov.uk/t/importing-streaming-api-swagger-fails/4828 "2022-02-10T12:54:19Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![ebrian101](http://forum.companieshouse.gov.uk/user_avatar/forum.companieshouse.gov.uk/ebrian101/32/1145_2.png) [@ebrian101](http://forum.companieshouse.gov.uk/u/ebrian101)\
**Post date:** [September 16, 2022, 12:31pm UTC](http://forum.companieshouse.gov.uk/t/importing-streaming-api-swagger-fails/4828/16 "2022-09-16T12:31:53Z")

</div>

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](http://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 formats of the API and there are inconsistencies and spelling mistakes in the API spec. Don’t rely on it as being perfect.

---

_[View the full topic](http://forum.companieshouse.gov.uk/t/importing-streaming-api-swagger-fails/4828)._