'Persons with significant control' resource specifications update

API Changes Information
1

Please be advised that changes have been made to several persons with significant control (PSC) specification reference/resource pages to ensure they accurately reflect existing GET request/response content which will enable us to develop enhanced, additional functionality in the future.

  1. Changes to ensure specification content accurately reflects GET request/response content.

The following pages have been updated:

These pages previously referenced the ‘id’ being called as the ‘psc_id’ e.g.

GET https://api.company-information.service.gov.uk/company/{company_number}/persons-with-significant-control/individual/{psc_id}

The ‘id’ actually being called for these resources is the ‘notification_id’ e.g.

GET https://api.company-information.service.gov.uk/company/{company_number}/persons-with-significant-control/individual/{notification_id}

For clarification, ‘psc_id’ is a unique ‘id’ for a PSC, ‘notification_id’ is a unique ‘id’ for an actual ‘notification’ (the PSC equivalent of an officer appointment).

N.B. THESE ARE TEXT CHANGES ONLY - they do not change the GET response content.

Why is this change being made?

  1. To enable enhanced, additional functionality in the future.

The following ‘new’ GET response content, that does contain a ‘psc_id’, will be added to several specification pages.

“links”: {
“persons_with_significant_control”: {
“notifications”: “string”
},

This is essentially the PSC equivalent of the links object data item that is currently present in officer GET responses e.g.

“links”: {
“officer”: {
“appointments”: “string”
},

See Companies House Public Data API: officerList as an example.

This additional content has been added to the following specification pages:

N.B.

  • This is early notification of expected future API GET response content.
  • Development of this future functionality is on-going so it is possible the new content may change. An additional forum post will be published to advise of changes if any occur.
  • Additional note for Streaming API customers: To ensure this new content is populated for all PSC notification resources we will need to publish a new event for all PSC resources. It is possible this will be a ‘bulk’ publication of events as previously undertaken to publish identity verification details.

Effective date:
This new content will be available no earlier than 22nd June 2026.