CleanCounts supports API access.
Every CleanCounts general subscription includes application programming interface (API) access, a value not often provided with other registries. The API lets you do everything programmatically that your user permissions allow you to do in the system.
How access works.
API access is included with every organizational general subscription. Every key is scoped to the permissions of the account that issued it, so programmatic access follows the same rules as the platform itself.
What the API does.
Issue
Upload generation data, including hourly data, and receive certificates for approved generation.
Transact
Transfer certificates between organizations, accept incoming transfers, and reserve or withdraw certificates for external programs.
Retire
Retire certificates for voluntary, compliance, or hourly claims.
Delegate
Grant defined authority to agents, reporting entities, and service providers.
Report
Pull your organization's certificates, transactions, and generator records whenever you need them.
Illustrative interface: the CleanCounts API Utility App
Who builds on it.
Generators automate their monthly and hourly generation reporting. Portfolio owners run bulk operations across hundreds of assets. Reporting entities submit data for the generators they represent. Different participants need different things from the API, and the permission model is built to serve each of them within their role.
Documentation and getting started.
Full API documentation covers authentication, endpoints, and sample requests. A sandbox environment is available for development and testing; contact an API technical specialist to get set up. To start building, email SystemAdmin@cleancounts.org and we will connect you with an API technical specialist.
Data quality.
API data is registry data: serialized certificates with full lifecycle traceability, generation validated through grid operators and qualified reporting entities (QREs), and attributes carried at the granular certificate level, from hour and location to fuel type and enhanced attributes. What you pull through the API is the same single record every other participant sees.