Your systems and your contractors’ systems, feeding one compliance record
Caldora Compliance takes data from the systems you and your contractors already run, so the evidence and records Ofgem can ask for build up without being typed in twice. You approve every connection, see everything it adds, and keep the sign-off.
Your own systems
Connect a CRM, billing platform, building management system or ticketing system with an API key issued to your organisation. It can:
- add complaints, incidents, corrective actions and priority services register entries to the right network;
- file evidence against a condition, which counts towards its checklist and updates its status;
- read your networks, complaints and incidents back.
On a network you share with another company, a key adds and reads only your own records.
Your managing agent’s and contractors’ systems
A firm you appoint can connect its own system, such as its billing or maintenance system, to your record:
- The firm asks. It names the system it wants to connect.
- You approve. Nothing works until an administrator at your organisation approves it.
- The firm collects its key once. Caldora keeps only a hash of it, so nobody can see it again.
The connection reaches exactly what the firm’s people can reach: the networks it is appointed to, evidence on the conditions its service works on, and only the record types its service covers. A metering and billing firm, for example, can add complaints and file evidence on the billing conditions, and nothing on fair pricing or cost allocation. It can never sign off, invite people or appoint firms.
You stay in control
| Approval | Every contractor connection waits for your approval, and appears in your daily email until you decide. |
| Visibility | Everything a connection adds is labelled with the firm and its system, and listed for you. |
| Ending it | End a connection at any time. Ending the firm's appointment stops its connection at once. |
| Sign-off | Only your own people sign conditions off. |
| Limits | 100 requests an hour per key; files up to 50 MB in the same formats as the app. |
For developers
A REST API at https://caldoracompliance.co.uk/api/external, authenticated with a bearer key. GET ?type=status lists the networks a key reaches and, for a contractor’s key, the conditions it can file evidence on and the record types it can add. Records are created with a JSON POST; evidence with a multipart POST ?type=evidence. The full reference is in the Caldora Compliance Platform Overview and API Guide, available on request.
Common questions
Can heat network compliance software take data from our own systems automatically?
Caldora Compliance has an API for your own systems, such as a CRM, billing platform or building management system. It adds complaints, incidents, corrective actions, priority services register entries and evidence to the right network, and reads your networks, complaints and incidents back.
Can our managing agent or contractors connect their systems?
Yes. An appointed firm asks to connect its system, you approve it, and the firm collects its key once. The connection reaches only the networks, conditions and record types the firm's appointment covers, everything it adds is labelled and listed for you, and you can end it at any time.
Does an API connection sign anything off?
No. Evidence sent by API counts towards a condition's checklist, but only your own people sign conditions off.
See also what each appointed firm sees.