POST /api/v1/installer/login) and scoped to a specific charge_point_id.
A typical commissioning flow:
- Start the session — triggers connectivity and configuration checks
- Poll status — monitor test progress
- Apply a template if standard checks fail
- Review logs and diagnostics to diagnose failures
- Report issues for hardware defects or site problems
- Commission when all checks pass (see Charge Points)
Start commissioning
POST /api/v1/installer/commissioning/{charge_point_id}/start
Kicks off a commissioning session for the charge point. The system runs a sequence of automated checks: OCPP connectivity, heartbeat, configuration validation, and a test transaction.
string
required
The unique identifier of the charge point to commission.
string
Optional commissioning template to apply before running checks. If omitted, the default template for the charge point model is used.
boolean
Set to
true to skip the test transaction step. Useful on sites where a vehicle is not available during commissioning. Defaults to false.202 Accepted
string
Unique identifier for this commissioning session.
string
Initial status is
running. Poll the status endpoint to track progress.array
Ordered list of commissioning steps with their individual statuses.
Get commissioning status
GET /api/v1/installer/commissioning/{charge_point_id}/status
Returns the current state of the active (or most recent) commissioning session for the charge point.
string
required
The charge point’s unique identifier.
200 OK
string
One of:
running, paused, completed, stopped, failed.string | null
passed or failed once the session is complete. null while still running.string
Individual step result:
pending, running, passed, failed, skipped.Stop commissioning
POST /api/v1/installer/commissioning/{charge_point_id}/stop
Stops the active commissioning session. Use this if you need to abort due to hardware or site issues.
200 OK
Pause commissioning
POST /api/v1/installer/commissioning/{charge_point_id}/pause
Pauses the running session at the current step. Useful when the charge point needs brief physical attention during commissioning.
200 OK
Resume commissioning
POST /api/v1/installer/commissioning/{charge_point_id}/resume
Resumes a paused commissioning session from where it left off.
200 OK
Restart commissioning
POST /api/v1/installer/commissioning/{charge_point_id}/restart
Starts a fresh commissioning session from the beginning, discarding the current session’s results.
string
Optionally switch to a different commissioning template for the new session.
202 Accepted — same schema as the start response.
Get commissioning logs
GET /api/v1/installer/commissioning/{charge_point_id}/logs
Returns detailed event logs for the current or most recent commissioning session. Useful for debugging failures.
string
required
The charge point’s unique identifier.
string
Retrieve logs for a specific historical session. Omit to get the most recent session’s logs.
string
Filter by log level:
debug, info, warn, error. Defaults to all levels.200 OK
Report an issue
POST /api/v1/installer/commissioning/{charge_point_id}/report-issue
Submits an issue report for a commissioning problem, flagging it for review by the Dynamo CSMS support team or the CPO.
string
required
The charge point’s unique identifier.
string
required
Issue category. One of:
hardware_defect, network_problem, configuration_error, site_issue, other.string
required
Detailed description of the issue. Minimum 20 characters.
string
required
One of:
low, medium, high, critical.string
The commissioning step where the issue occurred (e.g.
"configuration", "test_transaction").string[]
URLs of photos uploaded to document the issue (hardware damage, wiring, etc.).
201 Created
List issues
GET /api/v1/installer/commissioning/{charge_point_id}/issues
Returns all issue reports filed for this charge point.
200 OK
List commissioning templates
GET /api/v1/installer/commissioning/templates
Returns all available commissioning templates. Templates pre-configure OCPP parameters and commissioning steps for specific hardware models or deployment scenarios.
200 OK
Apply template
POST /api/v1/installer/commissioning/{charge_point_id}/apply-template
Applies a commissioning template to a charge point mid-session, pushing OCPP configuration keys defined in the template to the hardware.
string
required
The charge point’s unique identifier.
string
required
The ID of the template to apply.
200 OK
integer
Number of configuration keys successfully applied.
string[]
Keys that were not applied — usually because the firmware does not support them.
Get diagnostics
GET /api/v1/installer/commissioning/{charge_point_id}/diagnostics
Returns hardware and firmware diagnostic information reported by the charge point during commissioning. Useful for support escalations and firmware compatibility checks.
200 OK