Send a firmware update to an existing charge point

Sends an OCPP UpdateFirmware (or SignedUpdateFirmware when a signing certificate is provided) to the charge point. The charge point must be an OCPP integration and currently connected. The update runs asynchronously: a 204 means the command was queued, not that the firmware was installed. At most one update per charge point every 10 minutes; further calls return 429 with errorCode FIRMWARE_UPDATE_RATE_LIMITED. A call rejected with a 4xx does not count; a 5xx or timeout does, because the update may already be queued.

Clients may send an Idempotency-Key header for safe retry semantics; the header is currently accepted and ignored (no enforcement yet).

Required scope: charge-points-firmware:write. It must be granted by name; all does not include it.
Organization authorization: supported

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
int64
required
Body Params
string
required
length ≤ 512
(?i)^(https?|ftps?|sftp)://\S+$

URL the charge point downloads the firmware file from. Supported schemes: http, https, ftp, ftps, sftp.

string | null

PEM-encoded firmware signing certificate. When set, signature is required and a signed firmware update (OCPP 1.6 Security Extension / OCPP 2.0.1) is sent instead of a plain UpdateFirmware.

string | null

Base64-encoded firmware signature. Required when signingCertificate is set.

Headers
string

Opaque client-supplied key used for safe retries. Accepted today; behavior not yet enforced.

Responses
204

Firmware update sent to the charge point

429

A firmware update was sent to this charge point in the last 10 minutes

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json