If you've ever integrated with more than one UK government API, you already know the pain: each one has its own auth flow, its own error format, its own rate limits, its own quirks in sandbox vs production. HMRC alone has a dozen+ API families under Making Tax Digital, each slightly different from the last.
I got tired of solving this from scratch on every project, so I built GovBridge UK — a single gateway that normalizes HMRC MTD, Companies House, DVLA, and Land Registry behind one consistent interface.
What it handles:
A single error envelope across all four government APIs, instead of learning four different failure formats OAuth token management and refresh handled once, not per-integration 40+ working HMRC endpoints already wired up and sandbox-tested (Income Tax MTD, VAT, CIS, PAYE, Property/Savings income, and more) A developer portal (React) so you can explore and test endpoints without reading four separate sets of gov.uk docs
Stack: .NET 8/10, ASP.NET Core, PostgreSQL, Redis for token/session caching, React/TypeScript for the portal.
It's still evolving - security hardening and the CT600/GovTalk integration are in progress. If you've built anything against HMRC's MTD APIs, Companies House, or DVLA, I'd genuinely like to hear how you handled the integration overhead - did you roll your own, or is there something out there I've missed?
Top comments (0)