---
title: "Onboard charger: set installation to OCPP 1.6J authentication mode and configure URL"
method: POST
path: "/chargers/{chargerId}/onboarding"
tags: ["Charger settings"]
---

# Onboard charger: set installation to OCPP 1.6J authentication mode and configure URL

`POST /chargers/{chargerId}/onboarding`

## Request

- Base URL: `http://integrations.api.prod.zaptec.com`
- URL: `http://integrations.api.prod.zaptec.com/chargers/{chargerId}/onboarding`
- Auth: HTTP bearer

Onboards a charger for OCPP by updating the charger's installation authentication mode to OCPP using the provided `ocppUrl`.If `chargeBoxId` is provided, the endpoint also updates the charger setting for ChargeBoxId.Limitations and considerations:- `ocppUrl` must be a valid WebSocket URL (`ws://` or `wss://`).- The charger must be linked to an installation.You're about to switch the authentication type to OCPP 1.6J. Please note that OCPP 1.6J may incur 4G data consumption costs in the future. Reach out to your dedicated Zaptec Account Manager for more information.

## Path parameters

- `chargerId` string, uuid, required

## Request body

- ChargerOnboardingRequest
  - `ocppUrl` string, required
  - `chargeBoxId` string, nullable, required

## Response `204`

No Content

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `500`: Internal Server Error

---

[API](https://skmtc.dev/zaptec/apis/integrationsapi-v1.md) - [All operations](https://skmtc.dev/zaptec/apis/integrationsapi-v1/llms.txt) - [OpenAPI document](https://skmtc.dev/zaptec/apis/integrationsapi-v1/revisions/ddbf44002ba0?raw)