Tools (28)

Extracted live via the executor SDK.

• easee.easeeSessions

  Refer to easee.cloud API for details.

• greenPowerIndexGrNstromIndex.gsiBesthour

  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).

• greenPowerIndexGrNstromIndex.gsiDispatch

  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).
• greenPowerIndexGrNstromIndex.gsiMarketdata

  Compatible to awattar (https://api.awattar.de/v1/marketdata) API interface but data comes from GreenPowerIndex instead of EPEXSpot.

• greenPowerIndexGrNstromIndex.gsiPrediction

  Retrieval the GreenPowerIndex (GrünstromIndex) for a given city (by zipcode) in Germany.

• meteringDecorator.meteringGet

  Retrieves a metered reading using account (Stromkonto).

• meteringDecorator.meteringPost

  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).

• ocpp.ocppSessions

  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.

• openMeter.omActivities

  Provides a list of available meterrs in the OpenMETER project ( https://www.openmeter.de/ ) which grants access for analytics as data discovery.

• openMeter.omMeters

  Provides a list of available meterrs in the OpenMETER project ( https://www.openmeter.de/ ) which grants access for analytics as data discovery.

• openMeter.omReadings

  Provides a list of available meterrs in the OpenMETER project ( https://www.openmeter.de/ ) which grants access for analytics as data discovery.

• stromkontoLedger.prepareTransaction

  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.

• stromkontoLedger.stromkontoBalances

  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 www.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).

• stromkontoLedger.stromkontoChoices

  Signable choices (contract changes) for customer.

• stromkontoLedger.stromkontoLogin

  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.

• stromkontoLedger.stromkontoRegister

  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.

• stromQuittung.quittungComit

  Uses collected fields or provided fields to create a final receipt (Strom-Quittung).

• stromQuittung.quittungCreate

  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.

• stromQuittung.quittungPrepare

  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.

• stromQuittung.quittungTse

  Allows to retrieve all relevant data assiciated to a TSE service call. E.q. Input parameters, public key and signature.

• stromQuittung.quittungTseData

  Allows to retrieve input string for a signing process.

• stromQuittung.quittungTsEsignature

  Allows to retrieve digital signature for a given receipt.

• stromQuittung.quittungZugferd

  Allows to retrieve XML of the zugferd invoice.

• tariffPriceApi.tariffcomponents

  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

• tariffPriceApi.tariffSlpH0

  Provides pricing data for private households with standard load profiles (Standardlastprofil H0).

• wiMWechselprozesseImMesswesenStromStatusApi.wimstatus

  Access to status information of an existing metering change and allocation process.

• openapi.previewSpec

  Preview an OpenAPI document before adding it as a source

• openapi.addSource

  Add an OpenAPI source and register its operations as tools