Company Returns but Company Address Not Found

API Issues
1

The “Company profile” endpoint described here appears to be perfectly fine.

However, the “Registered office address” endpoint described here appears to return a 404 instead.

This occurs both in my application, and in Insomnia (HTTP Client).

Is anyone else having this issue, I believe it may be a bug?

This was working the other day, but seems to have suddenly broke, after some debugging I believe the problem is with the endpoint itself.

2

At the moment (2020-06-28 18:40) I also get 405 Method Not Allowed for these.

I don’t normally use this (company profile has this covered anyway). I thought I remembered another post saying the same a while back but can’t find it. Possibly coincidence but I don’t think I’ve ever seen this returned in the links section of the company profile endpoint (not that this proved anything).

I tried:

curl -uMY_API_KEY: "https://api.companieshouse.gov.uk/company/NF004299"
{
    "date_of_creation": "2008-11-18",
    "company_name": "PLATTS DRIEVAP ENGINEERING LIMITED",
    "type": "oversea-company",
    "undeliverable_registered_office_address": false,
    "registered_office_address": {
        "address_line_1": "10 Dargan Crescent",
        "address_line_2": "Belfast",
        "postal_code": "BT3 9JP"
    },
    "company_number": "NF004299",
    "jurisdiction": "united-kingdom",
    "etag": "7383e99a622ec09a92981cb4db514c5fa5accbf6",
    "company_status": "active",
    "links": {
        "self": "/company/NF004299",
        "filing_history": "/company/NF004299/filing-history",
        "officers": "/company/NF004299/officers",
        "uk_establishments": "/company/NF004299/uk-establishments"
    },
    ...
    }

But:

curl -uMY_API_KEY: "https://api.companieshouse.gov.uk/company/NF004299/registered-office-address"
HTTP/1.1 405 Method Not Allowed
Date: Sun, 28 Jun 2020 17:35:19 GMT
Connection: keep-alive
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: X-RateLimit-Query, origin, content-type, content-length, user-agent, host, accept, authorization
Access-Control-Expose-Headers: X-RateLimit-Window, X-RateLimit-Limit, X-RateLimit-Remain, X-RateLimit-Reset, Location, www-authenticate, cache-control, pragma, content-type, expires, last-modified
Access-Control-Max-Age: 3600
X-Ratelimit-Limit: 600
X-Ratelimit-Remain: 597
X-Ratelimit-Reset: 1593365982
X-Ratelimit-Window: 5m
Server: CompaniesHouse

Same story with e.g. https://api.companieshouse.gov.uk/company/00048839/registered-office-address

3

Hmm, not sure why you’re getting method not allowed, while I’m getting resource not found. That seems a bit odd. :thinking:

GET /company/NF004299/registered-office-address HTTP/2
Host: api.companieshouse.gov.uk
authorization: Basic REDACTED
user-agent: insomnia/2020.2.2
accept: */*

HTTP/2 404 
date: Mon, 29 Jun 2020 03:20:56 GMT
content-length: 0
access-control-allow-credentials: true
access-control-allow-headers: X-RateLimit-Query, origin, content-type, content-length, user-agent, host, accept, authorization
access-control-expose-headers: X-RateLimit-Window, X-RateLimit-Limit, X-RateLimit-Remain, X-RateLimit-Reset, Location, www-authenticate, cache-control, pragma, content-type, expires, last-modified
access-control-max-age: 3600
x-ratelimit-limit: 600
x-ratelimit-remain: 599
x-ratelimit-reset: 1593401156
x-ratelimit-window: 5m
server: CompaniesHouse

Meanwhile, I have decided I’ll just implement a fallback in my application, if the registered office address endpoint would like to work, I’d prefer it since it’s a smaller response and all I need, so until it’s verified that it should, or should not be working, I’ll probably continue using it and just have it request the company profile endpoint if getting the registered address office fails.

4

I will get this investigated.

1 Like
5

Yes can confirm that we are also now getting a 404, and this can be replicated on the documentation pages https://developer.companieshouse.gov.uk/api/docs/company/company_number/registered-office-address/readRegisteredOfficeAddress.html#here.

Any updates on when this might be resolved please?

Thanks

6

So sorry, this was broken by a deployment on Friday.
We will be applying a fix this morning.
I will let you know when it is in.

1 Like
7

This has now been resolved.
Apologies for any inconvenience caused.

1 Like
8

Probably not necessary, but just wanted to confirm that the endpoint is working for me again.

Thank you!