Choose what should work
Your developer defines the expected result, such as receiving a list of VAT deadlines.
GovBridge Assurance · Developer preview
GovBridge helps your team test connections between its software and UK government services, then compare the results before an update.
A developer sets up the checks. Your team reviews the reports. No live tax filing.
Illustrative test environment · Check version 1.0.0
Availability update, 10 October 2026: DVSA MOT history is now available. This video predates that release. See current service availability.
UK government data is spread across many services, each with its own sign-in, format and rules: Companies House, HMRC, HM Land Registry, the Food Standards Agency, DVSA, the EPC register and the Charity Commission. They come together in the GovBridge API.
One key, one way to ask, consistent JSON back. An example request searches Companies House for a company and receives an illustrative response.
What it serves. Available now: Companies House search, profiles, officers, PSC and filings; company verification with profile, officers and PSC in one call; HM Land Registry property sale history; Food Standards Agency hygiene ratings. Depends on provider access: DVSA MOT history, EPC energy ratings and the Charity Commission register. HMRC, test only: Making Tax Digital for VAT, Income Tax, CIS and savings, plus PAYE and Corporation Tax including CT600 via GovTalk, in the HMRC sandbox with synthetic data and no live filing.
GovBridge Assurance: know what changed before a software update. Run checks against a test system and compare each report with the last one. In an illustrative release review, two checks pass and the deadline field check fails as a regression since the previous report.
Built for UK software teams. For developers: one consistent API for supported UK government data. For delivery teams: clear reports on what passed, failed or could not finish, before a release.
GovBridge UK: UK government data and release checks, in one place. govbridge.co.uk. Developer preview. HMRC test environment only. Independent of government.
Your developer defines the expected result, such as receiving a list of VAT deadlines.
They run checks on a test system and upload a report with secrets and personal data removed.
Review passed, failed or incomplete checks and compare with the previous report. Your team decides what to fix.
Reports describe checks run by your team. They do not certify that the software is safe to launch, that tax figures are correct or that HMRC has approved it.
Passed: the expected result was seen. Failed: it did not match. Blocked: the check could not finish, for example because a service was unavailable.
Comparisons use matching test environments and check versions. A report checksum helps verify that the stored file has not changed; it does not independently verify the test.
Choose a path for your role, see a plain-language example, or discuss help setting up one software connection.
Already a developer? Run your first check · Explore supported government data APIs