Connecting a Zaptec Charger to Northe
1. Give Northe permission to access your charger
This is normally performed during the installation of the charge box however if it is not, then the driver can connect their own charger.
Step 1: Go to the Zaptec Portal
https://portal.zaptec.com/login/en
Step 2: Login to your Zaptec account
Step 3: Update charger permissions
Navigate from the Dashboard to the Installations page and a select a charger from the list.
Once you've selected a charger, navigate to the Permissions tab.
Click on the 'Give permission' button.
In the add permission section, go to the Partner tab and lookup 'Y8TU' and select 'Northe API', then click Next.
Choose user roles, by selecting both Owner & Service and then click Next.
Click Save to give Northe permission to access your charger.
Your charger is now connected to Northe.
2. Add the connected charger to a Northe account (For installers).
ℹ️ For customers, please see: How to connect my home charge box to my Northe account.
Step 1. Go to northe.app/activate
Activate the newly installed charge box for the customer by adding it to their Northe account via https://northe.app/activate.
Fill in the following information:
- Customer's email address
- Customer's Fleet Member ID
- Partner Key
Step 2. Add and connect the charge box
After logging in, you will be taken to the 'Add a new charge box' form where you can enter all of the details to add a charge box.
1. Type
Here you can change the charge box name and select the brand & model.
2. Charge Site
Create a charging site for the customers home address.
3. Connect Charge Box
Connect the charge box by adding the serial number of the charge box.
Please make sure you enter the correct charger serial number. Northe uses the serial number to connect the charger to the driver’s account. If an incorrect serial number is entered, the charger cannot be linked successfully and will remain offline in the app.
NOTE! Do not activate the stand-alone mode, as it may affect the connection to Northe and result in the charging session not being registered for reimbursement.