Base URL
Authentication
All requests must include theX-Api-Key header:
Data Model
The API is organized around three core resources that form a hierarchy:- Contracts represent energy agreements (e.g., PPAs) between a seller and a buyer. Contracts are polymorphic — the schema varies by type.
- Transactions represent the contractual energy volumes to be transferred between buyer and seller under a contract. Transactions are immutable; corrections produce a new version that supersedes the previous one.
- Nominations are the net saldo of valid transactions, aggregated by balance group and delivery period. Nominations are also versioned.
- Customers represent energy consumers or producers assigned to a BRP. Two customers make up either party of a contract. Customers can be approved, rejected, and configured with balance group settings.
Getting Started
- Obtain an API key from the BRP Portal.
- Explore your contracts and customers by calling
GET /v1/contractsandGET /v1/customers. - View transactions for a contract using
GET /v1/contracts/{contract_id}/transactions. - Check nominations with
GET /v1/nominations.
See API Conventions for details on pagination, error handling, timestamps, and rate limiting.