Enable this flag if you the CP is configured in plug and charge mode, it automatically starts a session when a car is plugged in, and the ID tag should not be authorized.

Cannot be enabled on personal charge points when the operator has "Enforce authentication on home chargers" enabled in its Home charging settings.

For users who have corporate billing with the same Partner as the Partner assigned to the charge point, the default payment method on this charge point will be the respective corporate billing account of the Partner.

When set to true, enables Uptime tracking for the charge point by creating an operational period.
When set to false or omitted, Uptime tracking remains disabled.

Requirements:

• Charge point must be commercial type (public or private)
• Operator must have operational availability enabled

Validation Errors:

• Returns HTTP 422 if charge point is personal type
• Returns HTTP 422 if operator has operational availability disabled

Examples:

{
  "name": "CP-001",
  "accessType": "public",
  "uptimeTrackingEnabled": true
}

Validation Error Examples:

Personal charge point error:

{
  "message": "The given data was invalid.",
  "errors": {
    "uptimeTrackingEnabled": [
      "Uptime tracking can only be enabled for commercial charge points"
    ]
  }
}

Operator settings error:

{
  "message": "The given data was invalid.",
  "errors": {
    "uptimeTrackingEnabled": [
      "Operator must have operational availability enabled to track uptime"
    ]
  }
}

When enabled, issues are created for hardware faults and connectivity problems, and notifications/webhooks are sent. When disabled, no issues are created and no notifications are sent for this charge point.

When enabled, the system automatically attempts to recover the charge point when hardware faults are detected (status requests, soft reboots). When disabled, issues are still created (if monitoring is enabled) but no automated recovery actions are taken.

DEPRECATED: Use monitoringEnabled and autoRecoveryEnabled instead. This field continues to work for backward compatibility, setting both new fields to the same value when provided. New integrations should use the new fields for independent control over monitoring and auto-recovery.