eMSP API: Creating tokens in be.ENERGISED

Creating CLIENT_ID and CLIENT_SECRET for the eMSP API has been significantly simplified in be.ENERGISED.

In which cases is the eMSP API useful?

Currently, the focus of the eMSP API is to read and retrieve invoices based on various filters. Additionally, information can be attached to close invoices and additional fields can be populated. The endpoints of the eMSP API will be expanded on an ongoing basis.

Authentication

Requests will only be processed if a valid JWT is provided as an authentication token. Every customer who wants to use this API has to configure such a token in be.ENERGISED. Exactly this process can be done with just a few clicks from now on.

What has changed in be.ENERGISED?

In be.ENERGISED, if you are using the eMSP API, you now have the option to create a new Access Token under Settings/System settings/eMSP API.

To do that, go to the "Create new token" button and then enter a name for it.

As soon as you click on "Save", the window with the "Client ID" and "Client Secret" opens. "Client Secret" will not be displayed to you afterwards, so copy this string out from this window. Both fields are grayed out and cannot be changed.

As soon as you close the window, the token appears with name and Client ID. The token is valid as long as it appears here. As soon as the token is deleted, it loses its validity.

More information about the eMSP API can be found here.