I’ve been using CH streaming API for approximately three years.
In every instance until 2025-02-01, the resource_id provided for a PSC in the streaming API was always associated with only a single company number.
As an example:
{
“data”: {
“etag”: “bbe75a1d629426f317aa830f41019363032a9826”,
“kind”: “corporate-entity-beneficial-owner”,
“name”: “Bridgestream Limited”,
“links”: {
“self”: “/company/OE022601/persons-with-significant-control/corporate-entity-beneficial-owner/xYFEp-BqcGdAf27fFKGxxWFUkPw”
},
“address”: {
“country”: “Jersey”,
“locality”: “St Helier”,
“postal_code”: “JE2 4TR”,
“address_line_1”: “40 Don Street”
},
“notified_on”: “2018-01-17”,
“identification”: {
“legal_form”: “Ordinary Resident Company”,
“legal_authority”: “Cayman Islands - The Companies Law”,
“place_registered”: “Registrar Of Companies Of The Cayman Islands,Cayman Islands”,
“country_registered”: “Cayman Islands”,
“registration_number”: “Cr 302844”
},
“natures_of_control”: [
“ownership-of-shares-more-than-25-percent-as-trust-registered-overseas-entity”,
“voting-rights-more-than-25-percent-as-trust-registered-overseas-entity”,
“right-to-appoint-and-remove-directors-as-trust-registered-overseas-entity”,
“significant-influence-or-control-as-trust-registered-overseas-entity”
],
“principal_office_address”: {
“country”: “Cayman Islands”,
“locality”: “Grand Cayman”,
“premises”: “One Nexus Way”,
“postal_code”: “KY1 1205”,
“address_line_1”: “P.O.Box 31243”,
“address_line_2”: “Camana Bay”
}
},
“event”: {
“type”: “changed”,
“timepoint”: 14259987,
“published_at”: “2025-02-01T10:08:02”
},
“resource_id”: “xYFEp-BqcGdAf27fFKGxxWFUkPw”,
“resource_uri”: “/company/OE022601/persons-with-significant-control/corporate-entity-beneficial-owner/xYFEp-BqcGdAf27fFKGxxWFUkPw”,
“resource_kind”: “corporate-entity-beneficial-owner”
}
where resource_id is indicated by the 3rd-from-the-last key/value pair and the company number is taken from the resource_uri value (in this case OE022601).
This has been true from timepoint 3600000 published on 2022-06-07 until 2025-02-01. On that date I observed the case that single resource_id was associated with two different company numbers.
The company numbers are OE022601 and OE023457.
This resource_id is present in 9 timepoints, 2 associated with the former company number and 7 with the latter, all published on 2025-02-01.
This non-uniqueness has not occurred since then either. So just one case in all this time.
Although a reading of the details of the PSC identified here indicates it is the same entity in all cases, this is not what occurred before, where even if the same entity is a PSC for distinct registered UK companies, it was identified by a different resource_id for each distinct UK company where it was a PSC.
It’s not documented (AFAIK) that resource_id will or will not be unique in the manner. But that’s been the practice.
Can someone shed some light on what occurred here? Is there an aberration? Or is there an intent to do something different with resource_id in the future?
Thanks