As a CPO, you will receive API requests to authorize remote charging sessions at your charging points.
To receive requests from Hubject you need to define where Hubject should send the requests in the portal. Please define the following settings:
- Authorization (for Remote Authorization)
- Reservation (if in use)
- PullAuthenticationData
Navigate to the Service Type Settings in the Administration section. Here you can define the endpoints of your web services. You can select different service types and change the settings for each service type. Click Edit in the top right corner to get started.
Authorization (mandatory)
The first service type you can modify is Authorization.
1. In the basic set of Authorization, neither Online Requests nor Broadcast request are included. These functions can be activated explicitly at this point. To do this, select Online Requests by ticking the box. Only then you can enter a Service URL or select Broadcast Request.
2. Set the following fields:
Online Requests: yes (please tick the checkbox). If this option is selected the HBS system will forward requests to your authorization URL endpoint.
Broadcast Request: no (please do not tick the checkbox).
Partner Service URL: type in the URL of your service endpoints (please make sure to avoid blank spaces)
3) Click Update Service Type to save your changes.
Please note that you can use 2 types of certificates for communication "Hubject backend -> your backend.
Hubject certificate (default value): Hubject will use the Hubject Certificate when requesting your EMP Backend. Please add it to your system's truststore to enable this option.
User certificate: Hubject will use the specific certificate uploaded in the certificate management section to communicate with your backend.
If you have selected the User certificate, you need to consign the certificate to your URL. The Common Name (CN) of the certificate should match your domain. For example, if your base URL is exampleurl.com the CN value entered should be the same. The HBS system does not have a list of trusted Certificate Authorities (CA) and needs this certificate.
Reservation (optional)
For the service type Reservation, you can enable Online Requests and then edit the Service URL to allow for the real-time authorization of remote reservation requests if your chargers support this functionality.
PullAuthenticationData (legacy)
This section is only used in very rare cases for CPOs who are unable to support real-time authorization and need to pull authentication data from the platform to allow users to charge.