4. Connect your service to an OCN Node
Last updated
Last updated
If you have followed the previous steps in this tutorial you should now have the following things ready for making your connection to the Open Charging Network:
(TOKEN_A in OCPI Terms)
There are three methods of interacting with the OCN Registry:
ocn-registry get-node 0xEada1b2521115e07578DBD9595B52359E9900104
Where 0xEada1b2521115e07578DBD9595B52359E9900104
is the operator's public address.
The Public URL could look something like this: https://test-node.emobilify.com
Once connected to the registry, you can use the getNode method to return the operator's public URL:
We will first send a GET request to the OCN Node’s versions endpoint, using the TOKEN_A we received from the faucet. Note that curl requests can be imported into e.g. Postman or Insomnia if desired.
Do the same for this endpoint:
You should see a long list of OCPI version 2.2 endpoints implemented by the OCN Node. You will want to save these endpoints for future reference in your application’s database.
For now though, we just need one endpoint. Find the endpoint URL for the module identifier “credentials”. This will be the one we use to connect to the node:
The OCN Node needs to know where to contact us in case there is a message from another party that needs to be routed to us. It can also help to filter requests, in the case that we have not implemented a specific OCPI module that another party is requesting from us.
This will create an authorization token that the OCN Node should use to access our own endpoints. It is logged on start. Be sure to make a note of the authorization token as we will need it later.
Note also the PUBLIC_IP
. We want the OCN Node to be able to access these endpoints from the outside, so we should make sure that the server is reachable via the public IP we set.
Now we are ready to connect to the OCN Node.
The credentials request is detailed below. Make sure to replace the variables TOKEN_A
, TOKEN_B
and PUBLIC_IP
, PARTY_ID
and COUNTRY_CODE
where described:
TOKEN_A
should match the one generated for you by the faucet
TOKEN_B
should match the authorization token that you have created
PUBLIC_IP
should point to your publicly accessible web service
If the request is successful, you should see a response with OCPI status code 1000 and the OCN Node’s credentials returned in the body.
Now that we have connected to the Open Charging Network we can make use of OCPI to find point of interest data, issue remote commands at charge points and authorize RFID cards of any other OCPI party that is connected to the network.
If you are using the on GitHub, you can check the Public URL of your selected OCN Node by doing this:
You can find documentation on how to install and use the library .
Please visit the for further details about this step.
Use the documentation provided to connect to the OCN Registry using the Java library.
You should see a JSON response with OCPI status code 1000. The response data will tell you that version 2.2 can be found at .
During the credentials handshake, the OCN Node will attempt to request our own versions and endpoints, just as we did before in
If you have not already done so, we can spin up a quick server and execite a node script that will display our versions and endpoints as follows (note: requires , and ):
PARTY_ID
and COUNTRY_CODE
refer to the same OCPI credentials that you used