Connect your own systems to CLRD. The API lets your CRM or tooling manage records and drive compliance jobs programmatically, so CLRD fits into your existing workflow instead of the other way round.

Clients, sites and jobs created through the API are stored in CLRD just like records created in the app — CRM-style, with the full lifecycle supported on every record — not a one-shot "job data in, document pack out" call. Download the generated document packs for review and manual submission, or optionally have CLRD submit them to the DNO for you.

• Manage your clients and sites — create, read and update them from your own system.
• Agencies can manage the installer companies they represent.
• Create and drive compliance jobs through their full lifecycle — validate & route to the correct G98/G99/G100 pathway, generate the DNO document pack, submit to the DNO, record the decision, and complete the post-installation notification. Jobs cover the full 2.0 device model: solar, batteries, V2G chargers, EV charge points and heat pumps (including load-only and mixed jobs), export/import limitation, and decommissioning — including removal-only jobs.
• Upload supporting documents to a job, and download the generated document packs and their files.
• Read job status, routing and full detail to sync progress back into your CRM.
• Look up ENA-registered devices — the generating units, EV charge points, heat pumps and stand-alone G100 limiters you can build a job from — to resolve them in your own system.
• Read and reply to the DNO message thread for a job — the submissions, the DNO's responses and your follow-ups — from your CRM.
• Deep-link into CLRD — a button on the CRM record can open the job's page in CLRD directly, in the user's own signed-in session, for everything your CRM doesn't re-implement.
• Receive webhooks — signed push notifications on job status changes and client/site edits — so your systems stay in sync without polling.

The API is authenticated with a per-account key and is available on the Volume Operations and Enterprise plans. Once your plan includes API access, create a key under Settings → API — the full endpoint reference then appears on this page.

Who the API is for. The API is for your own company's benefit: your team, and people building on your behalf, integrating CLRD with the systems you use — your own software or third-party tools connected to your account. Reselling API access, or building CLRD into a commercial software product sold to its own customers, requires our prior approval — if that's you, get in touch about a partner agreement before you integrate. See our Terms of Service for the full API terms.

To start building, request a CLRD Beta account for integration development and testing — DNO submission on the beta server is simulated only, so nothing your integration sends ever reaches a real DNO — then move to the production server once your integration is ready.