OCPP 1.6J Schemas — Core

Feature Profile: Core

Generated from the official OCA JSON schemas for OCPP 1.6 edition 2.
Field names, types, required status, enum values, and constraints are
extracted mechanically. No manual editing applied.

#Messages

• Authorize (CP → CS)
• BootNotification (CP → CS)
• ChangeAvailability (CS → CP)
• ChangeConfiguration (CS → CP)
• ClearCache (CS → CP)
• DataTransfer (CP ↔ CS)
• GetConfiguration (CS → CP)
• Heartbeat (CP → CS)
• MeterValues (CP → CS)
• RemoteStartTransaction (CS → CP)
• RemoteStopTransaction (CS → CP)
• Reset (CS → CP)
• StartTransaction (CP → CS)
• StatusNotification (CP → CS)
• StopTransaction (CP → CS)
• UnlockConnector (CS → CP)

#Authorize

Direction: CP → CS

Validate an idTag before or during a transaction.

#Authorize.req

{
  "idTag": "ABCDEF1234"
}

#Authorize.conf

idTagInfo object:

{
  "idTagInfo": {
    "status": "Accepted"
  }
}

#BootNotification

Direction: CP → CS

Charge Point registers with the Central System after (re)boot.

#BootNotification.req

{
  "chargePointModel": "ABCDEF1234",
  "chargePointVendor": "ABCDEF1234"
}

#BootNotification.conf

{
  "currentTime": "2024-01-15T10:30:00Z",
  "interval": 0,
  "status": "Accepted"
}

#ChangeAvailability

Direction: CS → CP

Change a connector or the entire Charge Point to operative/inoperative.

#ChangeAvailability.req

{
  "connectorId": 0,
  "type": "Inoperative"
}

#ChangeAvailability.conf

{
  "status": "Accepted"
}

#ChangeConfiguration

Direction: CS → CP

Set a configuration key on the Charge Point.

#ChangeConfiguration.req

{
  "key": "string",
  "value": "string"
}

#ChangeConfiguration.conf

{
  "status": "Accepted"
}

#ClearCache

Direction: CS → CP

Clear the Charge Point's authorization cache.

#ClearCache.req

No fields (empty object {}).

{}

#ClearCache.conf

{
  "status": "Accepted"
}

#DataTransfer

Direction: CP ↔ CS

Vendor-specific data exchange (bidirectional).

#DataTransfer.req

{
  "vendorId": "string"
}

#DataTransfer.conf

{
  "status": "Accepted"
}

#GetConfiguration

Direction: CS → CP

Read one or more configuration keys from the Charge Point.

#GetConfiguration.req

{}

#GetConfiguration.conf

configurationKey[] items:

{}

#Heartbeat

Direction: CP → CS

Keepalive — Charge Point signals it is still connected.

#Heartbeat.req

No fields (empty object {}).

{}

#Heartbeat.conf

{
  "currentTime": "2024-01-15T10:30:00Z"
}

#MeterValues

Direction: CP → CS

Send periodic or clock-aligned meter readings.

#MeterValues.req

meterValue[] items:

sampledValue[] items:

{
  "connectorId": 0,
  "meterValue": [
    {
      "sampledValue": [
        {
          "value": "string"
        }
      ],
      "timestamp": "2024-01-15T10:30:00Z"
    }
  ]
}

#MeterValues.conf

No fields (empty object {}).

{}

#RemoteStartTransaction

Direction: CS → CP

Central System requests the Charge Point to start a transaction.

#RemoteStartTransaction.req

chargingProfile object:

chargingSchedule object:

chargingSchedulePeriod[] items:

{
  "idTag": "ABCDEF1234"
}

#RemoteStartTransaction.conf

{
  "status": "Accepted"
}

#RemoteStopTransaction

Direction: CS → CP

Central System requests the Charge Point to stop a transaction.

#RemoteStopTransaction.req

{
  "transactionId": 0
}

#RemoteStopTransaction.conf

{
  "status": "Accepted"
}

#Reset

Direction: CS → CP

Reboot the Charge Point (Hard or Soft).

#Reset.req

{
  "type": "Hard"
}

#Reset.conf

{
  "status": "Accepted"
}

#StartTransaction

Direction: CP → CS

Charge Point reports that a transaction has started.

#StartTransaction.req

{
  "connectorId": 0,
  "idTag": "ABCDEF1234",
  "meterStart": 0,
  "timestamp": "2024-01-15T10:30:00Z"
}

#StartTransaction.conf

idTagInfo object:

{
  "idTagInfo": {
    "status": "Accepted"
  },
  "transactionId": 0
}

#StatusNotification

Direction: CP → CS

Charge Point reports a connector status or error change.

#StatusNotification.req

{
  "connectorId": 0,
  "errorCode": "ConnectorLockFailure",
  "status": "Available"
}

#StatusNotification.conf

No fields (empty object {}).

{}

#StopTransaction

Direction: CP → CS

Charge Point reports that a transaction has ended.

#StopTransaction.req

transactionData[] items:

sampledValue[] items:

{
  "meterStop": 0,
  "timestamp": "2024-01-15T10:30:00Z",
  "transactionId": 0
}

#StopTransaction.conf

idTagInfo object:

{}

#UnlockConnector

Direction: CS → CP

Remotely unlock a connector (for cable removal).

#UnlockConnector.req

{
  "connectorId": 0
}

#UnlockConnector.conf

{
  "status": "Unlocked"
}