← Back to docs
Verification Reports
GET/v1/reports/:id
Get a Verification Report
Reports are private and ownership-scoped — only the user who generated the report can retrieve it. The report hash in the response can be used to verify the snapshot has not been tampered with.
When to use it
Practical implementation contexts
Retrieve a stored evidence report by ID for compliance review
Verify the report hash matches the stored snapshot
Embed report evidence in internal tooling
Auth
Access model
Authentication
API key or session token
Request
curl https://api.entylink.com/v1/reports/vr_abc123def456gh78 \
-H "Authorization: Bearer etl_live_xxx"
Parameters
ParameterTypeDescription
idstringThe report public ID (vr_ prefix)
Response
Response exampleapplication/json
{
"data": {
"id": "vr_abc123def456gh78",
"company_number": "08804411",
"company_name": "REVOLUT LTD",
"outcome": {
"status": "pass",
"risk_level": "none",
"disclaimer": "This Verification Report is based on publicly available data from Companies House..."
},
"signals": [],
"evidence": {
"schema_version": "2026-05-01",
"report_hash": "sha256:3a7f9c...",
"source": "Companies House",
"source_url": "https://find-and-update.company-information.service.gov.uk/company/08804411",
"generated_at": "2026-05-03T12:00:00.000Z"
}
}
}Related pages
Keep moving from docs into implementation and evaluation
Next step
Move from docs into a real registry workflow.
Entylink is built for teams embedding UK company data, verification, and monitoring into products rather than manually browsing the register.