I’ve given examples of what I do below. I’ve shown this using cUrl on the command line but the REST URI is the same for other methods. I’ve included links so you can also see the data returned on the web in CH Beta.
If these don’t help you’ll need to give some more information about what you’re actually doing and what specifically you want to achieve. When you say “I tried with given data as follows” what was the REST URI (e.g. what endpoint / parameters were you trying)? When you say “But none of them got any response” what does that mean? An http error? No http error but nothing in the JSON body returned? etc.
For 2) if you use the “List the company persons with significant control statements” endpoint: (see https://developer.companieshouse.gov.uk/api/docs/company/company_number/persons-with-significant-control-statements/listPersonsWithSignificantControlStatements.html )
curl -u"my-api-key-goes-here:" "https://api.companieshouse.gov.uk/company/SC549056/persons-with-significant-control-statements"
The JSON response should be like:
{
“start_index”: 0,
“items”: [ {
“kind”: “persons-with-significant-control-statement”,
“statement”: “no-individual-or-entity-with-signficant-control”,
“etag”: “189067174ec5b114054a4249536f95e4d321773c”,
“notified_on”: “2016-11-01”,
“links”: { “self”: “/company/SC549056/persons-with-significant-control-statements/-NXsaUt_99YynFxAmDQ16ozDOHg” }
} ],
“active_count”: 1, “items_per_page”: 25,
“total_results”: 1, “ceased_count”: 0,
“links”: { “self”: “/company/SC549056/persons-with-significant-control-statements” }
}
You asked about the statement-id parameter. That would be used if you wanted to get a specific statement - but you’d need to find this first. You can do this for a given company number by using the “List the company persons with significant control statements” endpoint. I wouldn’t normally need to do this since the same information is already given in the previous endpoint e.g. the “text” of the statement is conveyed by the constant given in the member “statement”: “no-individual-or-entity-with-signficant-control”. If you wanted you can use the “links”: { “self”: “/company/SC549056/persons-with-significant-control-statements/-NXsaUt_99YynFxAmDQ16ozDOHg” } member to look up the entry for a particular statement - in this example you’d use:
curl -u"my-api-key-goes-here:" "https://api.companieshouse.gov.uk/company/SC549056/persons-with-significant-control-statements/-NXsaUt_99YynFxAmDQ16ozDOHg"
So the “self” member in the internal “links” member gives you the appropriate “get statement” endpoint (see https://developer.companieshouse.gov.uk/api/docs/company/company_number/persons-with-significant-control-statements/statement_id/getPersonsWithSignificantControlStatement.html )
You can see this example Beta (note that the part after “.gov.uk” has the same format as the REST API endpoint fragment):
For 3)
if you use the “List the company persons with significant control” endpoint: (see https://developer.companieshouse.gov.uk/api/docs/company/company_number/persons-with-significant-control/listPersonsWithSignificantControl.html )
curl -u"my-api-key-goes-here:" "https://api.companieshouse.gov.uk/company/02443921/persons-with-significant-control"
The JSON response should be like:
{
“items_per_page”: 25, “start_index”: 0, “active_count”: 3
“links”: { “self”: “/company/02443921/persons-with-significant-control” },
“ceased_count”: 0, “total_results”: 3,
“items”: [
{
“description”: “super-secure-persons-with-significant-control”,
“kind”: “super-secure-person-with-significant-control”,
“etag”: “0913bc1ce0f0833295114c4b89e997f89ba85445”,
“links”: { “self”: “/company/02443921/persons-with-significant-control/super-secure/NcZQQA0LMrXYV1u0fGRHLrGIL_I” }
},
{
“links”: { “self”: “/company/02443921/persons-with-significant-control/super-secure/JFL2DKSDumug-XdKsxukUZWRZYw” },
“description”: “super-secure-persons-with-significant-control”,
“kind”: “super-secure-person-with-significant-control”,
“etag”: “cd218d85b3989d9c19ec517b276b20ad03d64907”
},
{ … I’ve edited out the non-super-secure entry you also get }
],
}
Again, if you wanted you can use the links → self member on either of these to look up them individually (e.g. this is the super-secure-id bit you mentioned). I’d have no reason to - you gain no extra info at the moment - but if you liked you can take:
“links”: { “self”: “/company/02443921/persons-with-significant-control/super-secure/JFL2DKSDumug-XdKsxukUZWRZYw” }
And call this endpoint (see https://developer.companieshouse.gov.uk/api/docs/company/company_number/persons-with-significant-control/super-secure/super_secure_id/getSuperSecurePersonWithSignificantControl.html ):
curl -u"my-api-key-goes-here:" "https://api.companieshouse.gov.uk/company/02443921/persons-with-significant-control/super-secure/JFL2DKSDumug-XdKsxukUZWRZYw"
JSON response:
{
“links”: { “self”: “/company/02443921/persons-with-significant-control/super-secure/JFL2DKSDumug-XdKsxukUZWRZYw” },
“description”: “super-secure-persons-with-significant-control”,
“kind”: “super-secure-person-with-significant-control”,
“etag”: “cd218d85b3989d9c19ec517b276b20ad03d64907”
}
In Beta: https://beta.companieshouse.gov.uk/company/02443921/persons-with-significant-control
Note the two “Protected person with significant control” entries.