On 30 and 31 january, I observed timepoints without any data key in the returned JSON object.
For example, timepoint 90748417 of the companies data streaming api:
{
“event”: {
“type”: “deleted”,
“timepoint”: 90748417,
“published_at”: “2025-01-30T05:03:05”
},
“resource_id”: “SL037194”,
“resource_uri”: “/company/SL037194”,
“resource_kind”: “company-profile”
}
I observed this for 3 additional timepoints in the companies data streaming api:
90799078, 90799233, 90803026. And the same for the PSC streaming api timepoints 14246132, 14246133, and 14246134.
I’ve got timepoints on file going back to 46200000 for companies data and 3600000 for the PSC data, and I’ve never encountered this. In all other instances there is a data element, e.g.,
{
“data”: {
“etag”: “3f8b98586fdbbb22e640797fc7de7103b0501086”,
“type”: “registered-society-non-jurisdictional”,
“links”: {
… longer content deleted for compactness…
},
“event”: {
“type”: “deleted”,
“timepoint”: 90799032,
“published_at”: “2025-01-31T02:08:04”
},
“resource_id”: “RS009384”,
“resource_uri”: “/company/RS009384”,
“resource_kind”: “company-profile”
}
These are all ‘deleted’ event types. But without the ‘data’ section, there’s no etag, and so it’s not clear what to delete.
Any idea what’s going on here?