Corrently Green Energy API
Mock the Corrently Green Energy API with 26 endpoints without keys, sandboxes, or a live account.
[01]
About
Mock the Corrently Green Energy API as a turnkey Mockzilla sim with 26 OpenAPI endpoints, realistic JSON payloads, no upstream signup or sandbox keys. Corrently - from italian corrente, which is energy Introduction The Corrently ecosystem gets maintained by STROMDAO GmbH to support green energy services for prosumers, grid operators, regulators, integrators or any other party with an emerging need of consensus driven management. Methods: 16x GET, 10x POST. Top resource groups: Strom-Quittung, Stromkonto (Ledger), GreenPowerIndex (GrünstromIndex), TSE. Hit https://api.justmocks.com/corrently for the Mockzilla API Explorer landing and per-endpoint sample requests.
Endpoints
26 across 12 resource groups
Methods
GET 16 · POST 10 none deprecated
OpenAPI
3.0.2 spec version 2.0.0
Source spec
42 KB · YAML
view raw →
[02]
Endpoints
| GET |
/alternative/easee/lastSessions
|
Returns lastSession info for all easee wallboxes (chargers) given user has access to. Refer to easee.cloud API for details. Mocked via Mockzilla.
|
| GET |
/alternative/ocpp/lastSessions
|
Last Session Info Returns lastSession info of OCCP Cloud service for clearing in corrently ecosystem. Might be tested via OCPP cloud simulator. Last session Info of managed EV charging stations connected to the correnty ecosystem.
|
| GET |
/alternative/openmeter/activities
|
Public shared smart meters installed in Germany and available for subservices and exploration. Provides a list of available meterrs in the OpenMETER project ( https://openmeter.de/ ) which grants access for analytics as data discovery.
|
| GET |
/alternative/openmeter/meters
|
Public shared smart meters installed in Germany and available for subservices and exploration. Provides a list of available meterrs in the OpenMETER project ( https://openmeter.de/ ) which grants access for analytics as data discovery.
|
| GET |
/alternative/openmeter/readings
|
Public shared smart meters installed in Germany and available for subservices and exploration. Provides a list of available meterrs in the OpenMETER project ( https://openmeter.de/ ) which grants access for analytics as data discovery.
|
| GET |
/gsi/bestHour
|
Get best hour (with most regional green energy) in a given timeframe. Simple Wrapper around the GreenPowerIndex for easy integration into almost any SmartHome system that allows access to a JSON/REST Service This endpoint is designed to indicate if a device should be turned on or off. (Switch state). Available as a Mockzilla mock endpoint.
|
| GET |
/gsi/dispatch
|
Dispatch (Green Energy Distribution Schedule) Dispatch of green energy has two aspects to consider: - Availability of gerneration facility (depends on weather and installed capacity) - Demand of energy Using the green power index (GrünstromIndex) we have received a tool to automate distribution of energy in order to prevent redispatch situations. Doing this alows to opimize resource usage (tactical) and leverage data for investment planning (strategic).
|
| GET |
/gsi/marketdata
|
Marketdata Compatible to awattar (https://api.awattar.de/v1/marketdata) API interface but data comes from GreenPowerIndex instead of EPEXSpot.
|
| GET |
/gsi/prediction
|
Prediction Retrieval the GreenPowerIndex (GrünstromIndex) for a given city (by zipcode) in Germany.
|
| GET |
/metering/reading
|
Meter Reading Retrieves a metered reading using account (Stromkonto).
|
| POST |
/metering/reading
|
Meter Reading Post meter reading and get it decorated. Best practice is to first create a new Stromkonto with the register method and choose a nice secret to protect updates. Now regularly send updates to get readings (consumption) split into green power (1.8.1) and grey power (1.8.2). Mockzilla mock: no signup, no API key.
|
| POST |
/quittung/commit
|
Finishs a collection of data and finalizes receipt. Use this method after collecting all data via quittung/prepare Uses collected fields or provided fields to create a final receipt (Strom-Quittung).
|
| POST |
/quittung/create
|
Create a receipt for an energy delivery (only valid in Germany). Creates a full featured receipt (Quittung) for an energy delivery as it appears on a charging session or similar events. Allows to embed receipt generation directly into external services.
|
| POST |
/quittung/prepare
|
Allows to collect data with several requests (or a single) for a receipt. During the first call an account parameter will be returned within the result object. Any other parameter will be set inside the preperation. If account is put into body/request in following requests, the existing collection will be extended/updated with the provided body parameters/values.
|
| POST |
/quittung/tse
|
Retrieve TSE (Technische Sicherheitseinrichtung) Data for a given receipt (Strom-Quittung). Allows to retrieve all relevant data assiciated to a TSE service call. E.q. Input parameters, public key and signature.
|
| POST |
/quittung/tsedata
|
Retrieve TSE (Technische Sicherheitseinrichtung) raw data only for a given receipt (Strom-Quittung). Allows to retrieve input string for a signing process. Served by the Mockzilla mock runtime.
|
| POST |
/quittung/tsesignature
|
Retrieve TSE (Technische Sicherheitseinrichtung) Signature only for a given receipt (Strom-Quittung). Allows to retrieve digital signature for a given receipt.
|
| GET |
/quittung/zugferd
|
Retrieve Zugferd XML for a given receipt (Strom-Quittung). Allows to retrieve XML of the zugferd invoice.
|
| GET |
/stromkonto/balances
|
Balances Stromkonto represents a core component of the Corrently Ecosystem. It is a ledger for green energy related transactions and gets heavily used by the public Web-UI on stromkonto.net . Beside of some decoration and reformating operations all data is backed by the Energychain blockchain to provide consensus of balances and transactions. Use this API Endppoint if you prefere not to work with low level Distributed Ledger Technology (Blockchain).
|
| GET |
/stromkonto/choices
|
Selectable Choices for customer Signable choices (contract changes) for customer.
|
| POST |
/stromkonto/login
|
Login (via Mail) Sends a mail to a given email address to login this user. This function makes life a bit easier in order to not having to deal with private key protection on the user side as a shared key is used to sign transactions onbehalf of a particular account. However viewing consensus information (balances) are public and might move from account to account without prior notification. Best practice for third party uses is to always start a session with the login RESP call and only create a user in case the response indicates an unregistered status. Mocked via Mockzilla.
|
| POST |
/stromkonto/prepareTransaction
|
Prepare Transaction Prepares and inques a transaction (transfer) between two accounts (Stromkonten). This might be used to send any balanced entity. Using this endpoint will only prepare the transaction and enques it for signing and countersigning. This is done from within the user UI using validation process. Note: This API method does not validate any transations. In other words authentication, authorization, validation and actual transfer of value is done using a smart contract during processing in the energy blockchain.
|
| POST |
/stromkonto/register
|
Register (new Stromkonto) Calling this method with an unregistered (new) email will create a new account (Stromkonto) with all balances having a value of 0 and no transaction history. In addition some basic properties like region and zipcode are set to allow further operation of account.
|
| GET |
/tariff/components
|
Energy Tariff price components Provides insides into the different cost components of energy for a private household. Sample Request: https://api.corrently.io/v2.0/tariff/components?email=demo%40corrently.io&zip=69168&kwha=3300
|
| GET |
/tariff/slph0
|
Energy Tariff information Provides pricing data for private households with standard load profiles (Standardlastprofil H0).
|
| GET |
/wim/status
|
WiM Proess Informtion Access to status information of an existing metering change and allocation process. Available as a Mockzilla mock endpoint.
|
[03]
Related mocks
Anchore Engine API
Simulate the Anchore Engine API in seconds. This is the Anchore Engine API.
112 endpoints
·
data
Apache Airflow REST API
Mock the Apache Airflow REST API in seconds. Overview To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects.
73 endpoints
·
ai, data, devtools
ATO Business Registries API
Mock the ATO Business Registries API in seconds. Introduction The Business Registries API is built on HTTP.
74 endpoints
·
data, government