The ENAPI platform supports OCPI versions 2.1.1 and 2.2.1. The simplest way to connect is with our handshake user interface.
Setting up the OCPI connection
The user interface guides you through creating a new handshake. Click on "New handshake" to begin.
The ENAPI Transaction Broker can both send and receive OCPI connection requests. Connections can be made at any time. If needed, an integration call can be scheduled for support from ENAPI.
Both options will ask you about how you would like to configure the connection.
If you are connecting with OCPI version 2.2.1, you must specify whether the connection should use base64 encoding of authentication tokens. This is a configuration option, since not all platforms support it.
If you are connecting with OCPI version 2.1.1, you must specify whether the connection will be with your platform as Charge Point Operator (CPO) or eMobility Service Provider (eMSP).
💡 For platforms that have both CPO and eMSP market roles and use 2.1.1, a separate connection needs to be made for each one. OCPI 2.2.1 supports multiple roles over a single connection.
💡 For Charge Point Management Systems using OCPI 2.1.1, we support communication over a single connection, or multiple connections (for example in a multi-tenant setup).
For connections initiated by ENAPI
Once you have configured the connection options, you will be asked to input your platform's OCPI versions URL and the token A which ENAPI will use to authenticate itself on your system for versions and credentials requests.
Clicking on "Fetch versions" will first perform a GET request to your versions URL, followed by a GET request to your specified version details URL, displaying the supported OCPI modules ENAPI has found.
Clicking on "Perform Handshake" will send the POST credentials request to your credentials endpoint. You will see the status of the handshake attempt and, if successful, details about the connection.
You can also click on the 🔍 button to see logs in case a handshake attempt fails.
For connections initiated by your platform
Once you have configured the connection options, you will be presented with ENAPI's party information (country code and party ID), versions URL and the token (Token A) which you will need to authenticate the following requests to ENAPI:
GET versions: fetch available versions
GET version details: fetch endpoints for your desired OCPI version
POST credentials: request the exchange of credentials (i.e. handshake)
After the POST credentials request is successful, the "Token A" will be deleted and can no longer be used.
Next steps
Once a staging connection has been established, ENAPI will schedule a testing session to ensure production-readiness. The same handshake procedure will be needed for the setting up of the production connection.