I was surprised to discover that the api can return a “care_of_name” field as part of the registered office in both the companyProfile and registered-office-address responses.
There is an example of it here:
GET /company/02771869/registered-office-address
GET /company/02771869
This field isn’t mentioned in the resource for either of these calls and we have no way of knowing it exists beyond accidently stumbling across it. However, the C/O address is rendering in the Beta search site so it must be a “known quantity” as it were.
The Officer resource has a “care_of” field for officer addresses. However the only way I can check this is correct and it shouldn’t actually be “care_of_name” is to randomly look at company’s officerlist and hope to find one that has this field (I haven’t yet).
In general the problem here is twofold.
-
Without correct and current documentation we don’t even know what information could potentially be in a response from the API.
-
Even if we do know what information could potentially be in a response, we don’t know the rules for that information unless we can find an example and extrapolate from how it’s rendered in the beta search results.
These combined lead to a lot of trial and error. There are still some fields that I have scraped literally thousands of API responses looking for and haven’t found.