Zaptec charging stations support OCPP 1.6J, allowing integration with third-party backend systems. This enables external control over authentication, session management, and data flow.  

Zaptec offers two ways to connect charging stations to a backend using OCPP 1.6J. Choose the method that fits your requirements. For both methods, you’ll need a Zaptec account with service-level permissions or be the installation owner to configure this.

Enable OCPP 1.6J authentication (direct/box-level)

• Charging stations connect directly to the backend system.
• Your backend manages authentication, authorisation, and charging logic.
• Zaptec's smart features are disabled. Smart charging and load balancing will need to be managed by the backend.

How to enable:

1. Log in to the Zaptec Portal.
2. Go to your installation.
3. Ensure chargers are online and no active charging sessions are running.
4. Go to Settings > Authentication.
5. Select OCPP 1.6J authentication.
6. Enter the OCPP central system URL, following the required rules.
7. Click Save. 

See the detailed guide here. 

Enable OCPP 1.6J cloud authentication

• Charging stations connect to Zaptec cloud, which bridges to your backend.
• You can keep Zaptec's smart features (like load and phase balancing) while connecting to a backend or third-party system.
• Your backend receives OCPP messages via the Zaptec cloud.

How to enable:

1. Log in to the Zaptec Portal.
2. Go to your installation.
3. Go to Settings > Authentication.
4. Select OCPP 1.6J cloud authentication.
5. Enter the OCPP server URL and any required details
6. Click Save. 

See the detailed guide here. 

Parameters

• Server URL:  This is the WebSocket URL that the charging stations will connect to.  Use {deviceId} to automatically insert the charger's serial number.
  • Example: ws://ocpp.example.com/devices/{deviceId}
  • For ZCS000143, this becomes:  ws://ocpp.example.com/devices/ZCS000143
• Initial Device Password: Used for large installations to let the charging stations connect once. The OCPP backend can then set a new password remotely. Only needed if your backend requires it (OCPP-J 1.6, section 6.2.2).
• Default ID Tag: Auto-authorises all sessions using this tag. Works only if Authorisation Required is OFF. Leave it blank to require a physical charge card.

The OCPP URL set at the installation level applies to all charging stations in the installation and overrides any charger-specific URLs.

🔍 Legacy OCPP behaviour 

Zaptec charging stations identify themselves using basic authentication when connecting through OCPP. Depending on your URL setup and whether legacy behaviour is enabled, the charging stations will identify themselves using either the Device ID or the last part of the charger’s OCPP URL. 

For full details, including examples and fallback logic, see: 
Legacy OCPP Behaviour - Zaptec Developer Docs. 

Additional resources 

• Refer to Zaptec developer docs for complete technical details.

• Want to manage access in other ways? See access control and payment options. 

Updated 23 September 2025 09:58