Free developer tool · Browser-only validation
OCPP 1.6J message validator
Catch structural mistakes before a live charger test. Check CALL, CALLRESULT and CALLERROR envelopes, plus the supported request and response payloads for six common actions.
Validation result
Load an example or paste a single frame, then validate. Errors identify the field and expected structure without reproducing its value.
What this checker covers
OCPP 1.6J envelopes and selected payload fields: required fields, types, enums, field lengths, nested meter samples, unexpected fields and date-time syntax. Supported actions: BootNotification, Heartbeat, StatusNotification, StartTransaction, StopTransaction and MeterValues.
No request/response ID correlation, transaction-sequence checks, transport/security checks, full behavioural validation, vendor extensions or certification. Leap-second timestamps and integers outside JavaScript’s safe range are outside this preflight. CALLERROR details are checked as an object only.
Source: Open Charge Alliance OCPP 1.6 specifications and schemasHow to read an OCPP JSON envelope
A CALL has four items: message type 2, unique ID, action and payload object. A CALLRESULT has three: type 3, matching ID and payload. A CALLERROR has five: type 4, matching ID, error code, description and details object. This standalone checker does not know the preceding request, so you must identify the action for a response.
A structural pass is only the first check
Valid JSON cannot establish that a charger reconnects safely, reports accurate meter values or handles failed payments. Validate the actual hardware, firmware, operational flows and recovery conditions before production use. This independent preflight is not an Open Charge Alliance certification service.
