@ampeco/public-api-mcp 3.257.2 → 3.258.0

package/dist/generated/endpoints.json

@@ -1,5 +1,88 @@
 {
   "endpoints": [
+    {
+      "path": "/public-api/actions/admin/v1.0/{admin}/end-all-access",
+      "method": "POST",
+      "operationId": "adminEndAllAccess",
+      "summary": "Admin / End all access",
+      "description": "Experimental endpoint — not yet a stable contract. This action ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. End all browser sessions, remembered browser access and application access for the target administrator. This does not disable the administrator or prevent a new sign-in. The authenticated Public API principal must itself be a concrete human global or operator administrator, not an API-only administrator. The target must also be a concrete human global or operator administrator. Existing administrator-management permissions, role hierarchy and operator scope apply; another administrator is never substituted for the authenticated principal. The accepted operation durably records its progress. A `202` response does not guarantee that both browser sessions and application access have been ended: inspect `data.outcome` for the actual state. Pending work is retried independently with bounded backoff, up to five total attempts including the initial attempt. If work remains after the fifth attempt, the operation becomes `blocked` with `blockedReason` set to `retry_exhausted`. An operation also becomes `blocked` if its actor or subject is unavailable. A blocked outcome includes `blockedReason` when available. The response never includes a session count. No request body or includes are supported.",
+      "tags": [
+        "action / admin"
+      ],
+      "responses": {
+        "202": {
+          "description": "Accepted - the response contains the actual termination outcome"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        }
+      }
+    },
+    {
+      "path": "/public-api/actions/admin/v1.0/{admin}/terminate-sessions",
+      "method": "POST",
+      "operationId": "adminTerminateSessions",
+      "summary": "Admin / Terminate sessions",
+      "description": "Experimental endpoint — not yet a stable contract. This action ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. End the selected active tracked browser sessions for the target administrator. Unselected sessions, remembered browser access and application access are unchanged. The authenticated Public API principal must itself be a concrete human global or operator administrator, not an API-only administrator. The target must also be a concrete human global or operator administrator. Existing administrator-management permissions, role hierarchy and operator scope apply; another administrator is never substituted for the authenticated principal. Obtain session IDs from the administrator sessions listing. Supply between 1 and 100 distinct UUIDs. Every selected session must still be active and belong to the target administrator when the action executes. A `409` indicates a selection-state conflict, including a session that has ended, expired or no longer belongs to the eligible selection; no selected sessions are ended on conflict. A `422` indicates malformed input, including a missing, empty, oversized or duplicate selection, or a malformed UUID. A successful `202` response has `data.outcome` equal to `selected_sessions_ended` and includes `endedSessionCount`. Includes are not supported.",
+      "tags": [
+        "action / admin"
+      ],
+      "requestBody": {
+        "required": true,
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "sessionIds": {
+                  "type": "array",
+                  "items": {
+                    "type": "string",
+                    "format": "uuid"
+                  },
+                  "minItems": 1,
+                  "maxItems": 100,
+                  "uniqueItems": true,
+                  "description": "Distinct active browser session IDs belonging to the target administrator, obtained from the administrator sessions listing."
+                }
+              },
+              "required": [
+                "sessionIds"
+              ]
+            }
+          }
+        }
+      },
+      "responses": {
+        "202": {
+          "description": "Accepted - all selected sessions have been ended"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "409": {
+          "description": "The selected sessions are no longer all active sessions of the target administrator. No selected sessions were ended."
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        }
+      }
+    },
     {
       "path": "/public-api/actions/charge-point/v1.0/{chargePoint}/change-availability",
       "method": "POST",
@@ -3770,6 +3853,7 @@
                       "ChargePointSyncConfigurationNotification",
                       "CircuitConsumptionNotification",
                       "circuit.changed",
+                      "CoOperatorInsightChangedNotification",
                       "DiagnosticsStatusNotification",
                       "FirmwareStatusNotification",
                       "HardwareStatusNotification",
@@ -3809,7 +3893,8 @@
                       "cdr.received",
                       "chargingProfile.applied",
                       "installerJob.changed",
-                      "corporateBilling.limitReached"
+                      "corporateBilling.limitReached",
+                      "SignedFirmwareStatusNotification"
                     ]
                   }
                 },
@@ -3911,6 +3996,69 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/partner-discount-change/v1.0/{discountChange}/cancel",
+      "method": "POST",
+      "operationId": "partnerDiscountChangeCancel",
+      "summary": "Partner discount change / Cancel",
+      "description": "⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. Cancel a scheduled change without changing the current discount. No request body is required. Corporate billing must be enabled; any other state returns 409. A successful action returns an empty 202 response. **Required permission:** `Partners.update` on the visible parent partner. Missing, out-of-scope or wrong-parent identifiers return 404; a visible partner without edit permission returns 403.",
+      "tags": [
+        "action / partner discount change"
+      ],
+      "responses": {
+        "202": {
+          "description": "Accepted"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "409": {
+          "description": "The request could not be completed due to a conflict with the current state of the resource. The operation may succeed if retried."
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/actions/partner-discount-change/v1.0/{discountChange}/end-now",
+      "method": "POST",
+      "operationId": "partnerDiscountChangeEndNow",
+      "summary": "Partner discount change / End now",
+      "description": "⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. End an active limited change now and apply its revert discount atomically. No request body is required. Corporate billing must be enabled and the stored revertDiscount must be present; otherwise return 409 without changing the rate or change state. If an attempted revert rate save fails, return 424 after rollback, retaining the pre-action rate and change state. A successful action returns an empty 202 response. **Required permission:** `Partners.update` on the visible parent partner. Missing, out-of-scope or wrong-parent identifiers return 404; a visible partner without edit permission returns 403.",
+      "tags": [
+        "action / partner discount change"
+      ],
+      "responses": {
+        "202": {
+          "description": "Accepted"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "409": {
+          "description": "The request could not be completed due to a conflict with the current state of the resource. The operation may succeed if retried."
+        },
+        "424": {
+          "description": "The requested operation cannot be completed because something it depends on is currently unavailable, such as an external system (e.g., a charge point) that is disconnected or unreachable, or required reference data (e.g., an exchange rate) that is missing. The `message` property carries the reason."
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
     {
       "path": "/public-api/actions/partner-invite-corporate-billing-policy/v1.0/{corporateBillingPolicy}/disable",
       "method": "POST",
@@ -4127,6 +4275,60 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/partner-revenue/v1.0/{partnerRevenue}/set-custom-fields",
+      "method": "POST",
+      "operationId": "partnerRevenueSetCustomFields",
+      "summary": "Partner revenue / set custom fields",
+      "description": "⚠️ Experimental endpoint — not yet a stable contract. This action ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. Set the current custom field values of a partner revenue without changing the revenue's financial data. This action requires permission to view the revenue and the `PartnerRevenues.update-custom-fields` permission. Send a JSON object containing the required `customFields` object. Omitted identifiers remain unchanged, while `null` clears the corresponding value. When custom fields are enabled for partner revenues, an empty object succeeds as a no-op. Invalid or unavailable identifiers and invalid values return `422` validation errors keyed by `customFields.<identifier>`, and no submitted values are changed. If custom fields are disabled for the tenant or partner revenue, the action returns `412 Precondition Failed`, including for an empty object. A `404` response means the revenue was not found.",
+      "tags": [
+        "action / partner revenue"
+      ],
+      "requestBody": {
+        "required": true,
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "customFields": {
+                  "type": "object",
+                  "additionalProperties": true,
+                  "description": "Custom field values keyed by their administrator-defined identifiers. The accepted type for each identifier is defined by the tenant's custom field configuration. Boolean values are JSON booleans; text and long text values are strings; email values are email-formatted strings; URL values are HTTP or HTTPS URL strings; number values use canonical base-10 decimal strings from `-99999999999999.999999` through `99999999999999.999999` with up to six fractional digits and no insignificant trailing fractional zeroes; date values are ISO 8601 `YYYY-MM-DD` strings; date-time values are ISO 8601 timestamps with a UTC offset; and JSON values may use any JSON-serializable value. Decimal strings are the precision-safe number request representation. JSON numeric inputs remain accepted for compatibility, but their precision may depend on the client's number handling."
+                }
+              },
+              "required": [
+                "customFields"
+              ],
+              "additionalProperties": false
+            }
+          }
+        }
+      },
+      "responses": {
+        "202": {
+          "description": "Accepted - the response body contains the current v1.2 revenue listing item after applying the submitted values"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
     {
       "path": "/public-api/actions/partner-settlement-report/v1.0/{partnerSettlementReport}/issue-partner-invoice",
       "method": "POST",
@@ -8035,6 +8237,16 @@
             "schema": {
               "type": "object",
               "properties": {
+                "name": {
+                  "type": "string",
+                  "maxLength": 255,
+                  "description": "Optional notification name. Omission or an empty or spaces-only string leaves it unset. Surrounding whitespace is trimmed. Explicit null is rejected."
+                },
+                "description": {
+                  "type": "string",
+                  "maxLength": 1000,
+                  "description": "Optional internal-only plain-text description, not included in event payloads. Omission or an empty or spaces-only string leaves it unset. Surrounding whitespace is trimmed; internal line breaks are preserved. Explicit null is rejected."
+                },
                 "id": {
                   "type": "number"
                 },
@@ -8059,6 +8271,7 @@
                       "ChargePointSyncConfigurationNotification",
                       "CircuitConsumptionNotification",
                       "circuit.changed",
+                      "CoOperatorInsightChangedNotification",
                       "DiagnosticsStatusNotification",
                       "FirmwareStatusNotification",
                       "HardwareStatusNotification",
@@ -8098,7 +8311,8 @@
                       "cdr.received",
                       "chargingProfile.applied",
                       "installerJob.changed",
-                      "corporateBilling.limitReached"
+                      "corporateBilling.limitReached",
+                      "SignedFirmwareStatusNotification"
                     ]
                   }
                 },
@@ -8262,6 +8476,16 @@
             "schema": {
               "type": "object",
               "properties": {
+                "name": {
+                  "type": "string",
+                  "maxLength": 255,
+                  "description": "Optional notification name. Omission or an empty or spaces-only string leaves it unset. Surrounding whitespace is trimmed. Explicit null is rejected."
+                },
+                "description": {
+                  "type": "string",
+                  "maxLength": 1000,
+                  "description": "Optional internal-only plain-text description, not included in event payloads. Omission or an empty or spaces-only string leaves it unset. Surrounding whitespace is trimmed; internal line breaks are preserved. Explicit null is rejected."
+                },
                 "id": {
                   "type": "number"
                 },
@@ -8286,6 +8510,7 @@
                       "ChargePointSyncConfigurationNotification",
                       "CircuitConsumptionNotification",
                       "circuit.changed",
+                      "CoOperatorInsightChangedNotification",
                       "DiagnosticsStatusNotification",
                       "FirmwareStatusNotification",
                       "HardwareStatusNotification",
@@ -8325,7 +8550,8 @@
                       "cdr.received",
                       "chargingProfile.applied",
                       "installerJob.changed",
-                      "corporateBilling.limitReached"
+                      "corporateBilling.limitReached",
+                      "SignedFirmwareStatusNotification"
                     ]
                   }
                 },
@@ -8783,116 +9009,155 @@
       }
     },
     {
-      "path": "/public-api/resources/authorizations/v1.0/{authorization}",
+      "path": "/public-api/resources/admins/v1.0/{admin}/sessions",
       "method": "GET",
-      "operationId": "authorizationReadDeprecated",
-      "summary": "Authorization / Read",
-      "deprecated": true,
+      "operationId": "adminSessionsListing",
+      "summary": "Admin / List active sessions",
+      "description": "Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. List active tracked browser sessions for the target administrator. Sessions that have ended, expired or been invalidated by a session-version change are excluded. This listing does not include application credentials or untracked browser sessions. The authenticated Public API principal must itself be a concrete human global or operator administrator, not an API-only administrator. The target must also be a concrete human global or operator administrator. Existing administrator-view permissions, role hierarchy and operator scope apply; another administrator is never substituted for the authenticated principal. Results use cursor pagination only and are ordered by descending session ID. Use the returned IDs with the terminate-sessions action. The listing is a snapshot: a session may become ineligible before a termination request executes. Includes are not supported.",
       "tags": [
-        "resource / authorizations"
-      ],
-      "parameters": {
-        "path": {
-          "authorization": {
-            "description": "The authorization ID to fetch",
-            "type": "string",
-            "required": true
-          }
-        }
-      },
-      "responses": {
-        "200": {
-          "description": "Success"
-        },
-        "401": {
-          "description": "Access token is missing or invalid"
-        },
-        "403": {
-          "description": "You do not have permission to perform the action"
-        },
-        "404": {
-          "description": "The record is not found"
-        },
-        "429": {
-          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
-        }
-      }
-    },
-    {
-      "path": "/public-api/resources/authorizations/v2.0",
-      "method": "GET",
-      "operationId": "authorizationsListing",
-      "summary": "Authorizations / Listing",
-      "description": "**Deprecated:** Use v2.1 endpoint instead. This endpoint does not distinguish between RFID and MAC address (Autocharge) authorizations - both return `id_tag` as the method.",
-      "deprecated": true,
-      "tags": [
-        "resource / authorizations"
+        "resource / admins"
       ],
       "parameters": {
         "query": {
-          "filter": {
-            "schema": {
-              "type": "object",
-              "properties": {
-                "operatorId": {
-                  "example": "1",
-                  "oneOf": [
-                    {
-                      "type": "string",
-                      "format": "integer"
-                    },
-                    {
-                      "type": "array",
-                      "items": {
-                        "type": "string",
-                        "format": "integer"
-                      }
-                    }
-                  ],
-                  "description": "Filter by operator ID(s). **For operator-scoped tokens:** If provided, must match the token's operator. Returns empty results if a different operator ID is specified. **For global admin tokens:** Returns resources from the specified operator(s). Multiple IDs can be provided to filter by multiple operators. **Usage examples:** - Single operator: `?filter[operatorId]=1` - Multiple operators: `?filter[operatorId][]=1&filter[operatorId][]=2`"
-                },
-                "createdAfter": {
-                  "type": "string",
-                  "format": "date-time",
-                  "description": "ISO 8601 formatted date. Lists only the authorizations created after this datetime"
-                },
-                "createdBefore": {
-                  "type": "string",
-                  "format": "date-time",
-                  "description": "ISO 8601 formatted date. Lists only the authorizations created before this datetime"
-                },
-                "lastUpdatedAfter": {
-                  "type": "string",
-                  "format": "date-time",
-                  "description": "ISO 8601 formatted date. Lists only the authorizations that were last updated after this datetime"
-                },
-                "lastUpdatedBefore": {
-                  "type": "string",
-                  "format": "date-time",
-                  "description": "ISO 8601 formatted date. Lists only the authorizations that were last updated before this datetime"
-                },
-                "status": {
-                  "type": "string",
-                  "description": "Lists only authorizations with one of the following statuses: \"accepted\", \"rejected\", \"pending\""
-                },
-                "method": {
-                  "type": "string",
-                  "description": "Lists only authorizations with one of the following methods: \"user_device\", \"id_tag\", \"mac_address\", \"admin\", \"plug_and_charge\", \"roaming\", \"payment_terminal\", \"plug_and_charge_iso15118\""
-                },
-                "partnerId": {
-                  "type": "integer",
-                  "description": "Lists only authorizations of users who are associated to a particular partner"
-                }
-              }
-            }
-          },
-          "page": {
-            "description": "DEPRECATED - Sunset date: Mon, 01 Jun 2026 The page number to fetch (defaults to 1). Not used in cursor pagination. **This parameter is deprecated and will be removed on Mon, 01 Jun 2026.** Use cursor pagination instead for better performance and consistency. See the cursor parameter below for details.",
-            "type": "integer",
-            "default": 1
-          },
           "per_page": {
-            "description": "The numbers of items to return. Used in both page and cursor pagination to declare the page size.",
+            "description": "The number of items to return per page.",
+            "type": "integer",
+            "minimum": 1,
+            "maximum": 100,
+            "default": 100
+          },
+          "cursor": {
+            "description": "The cursor to fetch the next page. **Do not construct this value manually.** Use one of the following methods: - Use the value from the previous response's `links.next` to fetch the next page - Pass an empty string (e.g., `?cursor` or `?cursor=`) to initiate cursor pagination on the first page",
+            "type": "string"
+          }
+        }
+      },
+      "responses": {
+        "200": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        }
+      }
+    },
+    {
+      "path": "/public-api/resources/authorizations/v1.0/{authorization}",
+      "method": "GET",
+      "operationId": "authorizationReadDeprecated",
+      "summary": "Authorization / Read",
+      "deprecated": true,
+      "tags": [
+        "resource / authorizations"
+      ],
+      "parameters": {
+        "path": {
+          "authorization": {
+            "description": "The authorization ID to fetch",
+            "type": "string",
+            "required": true
+          }
+        }
+      },
+      "responses": {
+        "200": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/resources/authorizations/v2.0",
+      "method": "GET",
+      "operationId": "authorizationsListing",
+      "summary": "Authorizations / Listing",
+      "description": "**Deprecated:** Use v2.1 endpoint instead. This endpoint does not distinguish between RFID and MAC address (Autocharge) authorizations - both return `id_tag` as the method.",
+      "deprecated": true,
+      "tags": [
+        "resource / authorizations"
+      ],
+      "parameters": {
+        "query": {
+          "filter": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "operatorId": {
+                  "example": "1",
+                  "oneOf": [
+                    {
+                      "type": "string",
+                      "format": "integer"
+                    },
+                    {
+                      "type": "array",
+                      "items": {
+                        "type": "string",
+                        "format": "integer"
+                      }
+                    }
+                  ],
+                  "description": "Filter by operator ID(s). **For operator-scoped tokens:** If provided, must match the token's operator. Returns empty results if a different operator ID is specified. **For global admin tokens:** Returns resources from the specified operator(s). Multiple IDs can be provided to filter by multiple operators. **Usage examples:** - Single operator: `?filter[operatorId]=1` - Multiple operators: `?filter[operatorId][]=1&filter[operatorId][]=2`"
+                },
+                "createdAfter": {
+                  "type": "string",
+                  "format": "date-time",
+                  "description": "ISO 8601 formatted date. Lists only the authorizations created after this datetime"
+                },
+                "createdBefore": {
+                  "type": "string",
+                  "format": "date-time",
+                  "description": "ISO 8601 formatted date. Lists only the authorizations created before this datetime"
+                },
+                "lastUpdatedAfter": {
+                  "type": "string",
+                  "format": "date-time",
+                  "description": "ISO 8601 formatted date. Lists only the authorizations that were last updated after this datetime"
+                },
+                "lastUpdatedBefore": {
+                  "type": "string",
+                  "format": "date-time",
+                  "description": "ISO 8601 formatted date. Lists only the authorizations that were last updated before this datetime"
+                },
+                "status": {
+                  "type": "string",
+                  "description": "Lists only authorizations with one of the following statuses: \"accepted\", \"rejected\", \"pending\""
+                },
+                "method": {
+                  "type": "string",
+                  "description": "Lists only authorizations with one of the following methods: \"user_device\", \"id_tag\", \"mac_address\", \"admin\", \"plug_and_charge\", \"roaming\", \"payment_terminal\", \"plug_and_charge_iso15118\""
+                },
+                "partnerId": {
+                  "type": "integer",
+                  "description": "Lists only authorizations of users who are associated to a particular partner"
+                }
+              }
+            }
+          },
+          "page": {
+            "description": "DEPRECATED - Sunset date: Mon, 01 Jun 2026 The page number to fetch (defaults to 1). Not used in cursor pagination. **This parameter is deprecated and will be removed on Mon, 01 Jun 2026.** Use cursor pagination instead for better performance and consistency. See the cursor parameter below for details.",
+            "type": "integer",
+            "default": 1
+          },
+          "per_page": {
+            "description": "The numbers of items to return. Used in both page and cursor pagination to declare the page size.",
             "type": "integer",
             "minimum": 1,
             "maximum": 100,
@@ -9661,6 +9926,9 @@
         "403": {
           "description": "You do not have permission to perform the action"
         },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
         "429": {
           "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
         }
@@ -9688,6 +9956,9 @@
         "404": {
           "description": "The record is not found"
         },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
         "429": {
           "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
         }
@@ -12727,15 +12998,135 @@
                   "type": "boolean",
                   "description": "When disabled, this EVSE will not be listed or counted in the Faults & connectivity loss widget or lens. The charge point will still appear for charge point-level faults (network loss, hardware faulted). Defaults to true."
                 },
-                "powerOptions": {
+                "externalId": {
+                  "type": "string"
+                },
+                "capabilityOverrides": {
                   "type": "object",
                   "properties": {
-                    "maxOutputVoltage": {
-                      "type": "integer",
-                      "minimum": 1,
-                      "maximum": 1000,
-                      "description": "Maximum output voltage for DC charging."
+                    "rfidReader": {
+                      "type": "string",
+                      "enum": [
+                        "auto",
+                        "force_enable",
+                        "force_disable"
+                      ],
+                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
                     },
+                    "creditCardPayable": {
+                      "type": "string",
+                      "enum": [
+                        "auto",
+                        "force_enable",
+                        "force_disable"
+                      ],
+                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    },
+                    "contactlessCardSupport": {
+                      "type": "string",
+                      "enum": [
+                        "auto",
+                        "force_enable",
+                        "force_disable"
+                      ],
+                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    },
+                    "debitCardPayable": {
+                      "type": "string",
+                      "enum": [
+                        "auto",
+                        "force_enable",
+                        "force_disable"
+                      ],
+                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    },
+                    "chipCardSupport": {
+                      "type": "string",
+                      "enum": [
+                        "auto",
+                        "force_enable",
+                        "force_disable"
+                      ],
+                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    },
+                    "pedTerminal": {
+                      "type": "string",
+                      "enum": [
+                        "auto",
+                        "force_enable",
+                        "force_disable"
+                      ],
+                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    },
+                    "remoteStartStop": {
+                      "type": "string",
+                      "enum": [
+                        "auto",
+                        "force_enable",
+                        "force_disable"
+                      ],
+                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    },
+                    "unlockCapable": {
+                      "type": "string",
+                      "enum": [
+                        "auto",
+                        "force_enable",
+                        "force_disable"
+                      ],
+                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    },
+                    "reservable": {
+                      "type": "string",
+                      "enum": [
+                        "auto",
+                        "force_enable",
+                        "force_disable"
+                      ],
+                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    },
+                    "chargingProfileCapable": {
+                      "type": "string",
+                      "enum": [
+                        "auto",
+                        "force_enable",
+                        "force_disable"
+                      ],
+                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    },
+                    "chargingPreferencesCapable": {
+                      "type": "string",
+                      "enum": [
+                        "auto",
+                        "force_enable",
+                        "force_disable"
+                      ],
+                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    },
+                    "startSessionConnectorRequired": {
+                      "type": "string",
+                      "enum": [
+                        "auto",
+                        "force_enable",
+                        "force_disable"
+                      ],
+                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    },
+                    "tokenGroupCapable": {
+                      "type": "string",
+                      "enum": [
+                        "auto",
+                        "force_enable",
+                        "force_disable"
+                      ],
+                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    }
+                  },
+                  "description": "Manual overrides for individual EVSE capabilities. Each property is independent. Send `force_enable` or `force_disable` to set or replace an override. Send `auto` to clear an existing override (the capability returns to automated detection). Omit a property to leave its current override unchanged."
+                },
+                "powerOptions": {
+                  "type": "object",
+                  "properties": {
                     "maxPower": {
                       "type": "integer",
                       "nullable": true,
@@ -12748,6 +13139,7 @@
                         "380",
                         "400",
                         "480",
+                        "600",
                         "120",
                         "208",
                         "240",
@@ -12796,134 +13188,22 @@
                       ],
                       "nullable": true,
                       "description": "Specifies the active line conductors used in the circuit. - `L1_L2` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L2_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L2` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L3` - Valid when `phases` = `single_phase` in electrical configuration `star`"
-                    }
-                  }
-                },
-                "externalId": {
-                  "type": "string"
-                },
-                "capabilityOverrides": {
-                  "type": "object",
-                  "properties": {
-                    "rfidReader": {
-                      "type": "string",
-                      "enum": [
-                        "auto",
-                        "force_enable",
-                        "force_disable"
-                      ],
-                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
-                    },
-                    "creditCardPayable": {
-                      "type": "string",
-                      "enum": [
-                        "auto",
-                        "force_enable",
-                        "force_disable"
-                      ],
-                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
-                    },
-                    "contactlessCardSupport": {
-                      "type": "string",
-                      "enum": [
-                        "auto",
-                        "force_enable",
-                        "force_disable"
-                      ],
-                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
-                    },
-                    "debitCardPayable": {
-                      "type": "string",
-                      "enum": [
-                        "auto",
-                        "force_enable",
-                        "force_disable"
-                      ],
-                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
-                    },
-                    "chipCardSupport": {
-                      "type": "string",
-                      "enum": [
-                        "auto",
-                        "force_enable",
-                        "force_disable"
-                      ],
-                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
-                    },
-                    "pedTerminal": {
-                      "type": "string",
-                      "enum": [
-                        "auto",
-                        "force_enable",
-                        "force_disable"
-                      ],
-                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
-                    },
-                    "remoteStartStop": {
-                      "type": "string",
-                      "enum": [
-                        "auto",
-                        "force_enable",
-                        "force_disable"
-                      ],
-                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
                     },
-                    "unlockCapable": {
-                      "type": "string",
-                      "enum": [
-                        "auto",
-                        "force_enable",
-                        "force_disable"
-                      ],
-                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
-                    },
-                    "reservable": {
-                      "type": "string",
-                      "enum": [
-                        "auto",
-                        "force_enable",
-                        "force_disable"
-                      ],
-                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
-                    },
-                    "chargingProfileCapable": {
-                      "type": "string",
-                      "enum": [
-                        "auto",
-                        "force_enable",
-                        "force_disable"
-                      ],
-                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
-                    },
-                    "chargingPreferencesCapable": {
-                      "type": "string",
-                      "enum": [
-                        "auto",
-                        "force_enable",
-                        "force_disable"
-                      ],
-                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
-                    },
-                    "startSessionConnectorRequired": {
-                      "type": "string",
-                      "enum": [
-                        "auto",
-                        "force_enable",
-                        "force_disable"
-                      ],
-                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    "maxOutputVoltage": {
+                      "type": "integer",
+                      "minimum": 1,
+                      "maximum": 1000,
+                      "nullable": true,
+                      "description": "Maximum output voltage for DC charging, in V. Leave empty to share the input voltage via roaming connections. Only relevant for the dc current type - providing a value for any other current type is rejected with a validation error."
                     },
-                    "tokenGroupCapable": {
-                      "type": "string",
-                      "enum": [
-                        "auto",
-                        "force_enable",
-                        "force_disable"
-                      ],
-                      "description": "Override value for an EVSE capability: - **auto**: Use automated detection logic (default) - **force_enable**: Always include this capability - **force_disable**: Never include this capability"
+                    "efficiencyPercent": {
+                      "type": "number",
+                      "minimum": 90,
+                      "maximum": 100,
+                      "description": "Stored efficiency override for a local DC EVSE. Supply a number from 90 to 100; invalid supplied local values return 422. Values are rounded to two decimal places when stored and take effect on the next DLM cycle. Without an override, DLM uses 95% for calculations. Omit this property for no override. Roaming EVSEs ignore this property."
                     }
                   },
-                  "description": "Manual overrides for individual EVSE capabilities. Each property is independent. Send `force_enable` or `force_disable` to set or replace an override. Send `auto` to clear an existing override (the capability returns to automated detection). Omit a property to leave its current override unchanged."
+                  "description": "Optional efficiencyPercent sets a stored override for a local DC EVSE. Supply a number from 90 to 100; invalid supplied local values return 422. Values are rounded to two decimal places when stored and applied on the next DLM cycle; without an override DLM uses 95%. Roaming EVSEs ignore this property. Omit the property for no override."
                 }
               },
               "required": [
@@ -13112,78 +13392,6 @@
                   "type": "boolean",
                   "description": "When disabled, this EVSE will not be listed or counted in the Faults & connectivity loss widget or lens. The charge point will still appear for charge point-level faults (network loss, hardware faulted). Defaults to true."
                 },
-                "powerOptions": {
-                  "type": "object",
-                  "properties": {
-                    "maxOutputVoltage": {
-                      "type": "integer",
-                      "minimum": 1,
-                      "maximum": 1000,
-                      "description": "Maximum output voltage for DC charging."
-                    },
-                    "maxPower": {
-                      "type": "integer",
-                      "nullable": true,
-                      "description": "Maximum power of the EVSE in W (Watts)."
-                    },
-                    "maxVoltage": {
-                      "type": "string",
-                      "enum": [
-                        "230",
-                        "380",
-                        "400",
-                        "480",
-                        "120",
-                        "208",
-                        "240",
-                        "110-130",
-                        "220-240",
-                        "277"
-                      ],
-                      "nullable": true,
-                      "description": "The maximum intake (input) voltage of the EVSE. For the ac current type the output voltage is the same as this intake voltage, while for the dc current type the output voltage can differ and is exposed separately in maxOutputVoltage. The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
-                    },
-                    "maxAmperage": {
-                      "type": "number",
-                      "nullable": true
-                    },
-                    "phases": {
-                      "type": "string",
-                      "enum": [
-                        "single_phase",
-                        "three_phase",
-                        "split_phase"
-                      ],
-                      "nullable": true
-                    },
-                    "phaseRotation": {
-                      "type": "string",
-                      "enum": [
-                        "RST",
-                        "RTS",
-                        "SRT",
-                        "STR",
-                        "TRS",
-                        "TSR"
-                      ],
-                      "nullable": true,
-                      "description": "`R` stands for `L1`, </br> `S` - for `L2` </br> `T` - for `L3` </br> So for example `RST` = `L1`, `L2`, `L3`, while `RTS` = `L1`, `L3`, `L2`, etc. </br> We are deriving the connected phase from this property for single phase if connectedPhase is not provided. Please don't rely on this property anymore as this functionality will be turned of in near future. Pass the correct connectedPhase instead. If you pass both properties (connectedPhase and phaseRotation) only connectedPhase will be taken into consideration for determining the phase."
-                    },
-                    "connectedPhase": {
-                      "type": "string",
-                      "enum": [
-                        "L1",
-                        "L2",
-                        "L3",
-                        "L1_L2",
-                        "L1_L3",
-                        "L2_L3"
-                      ],
-                      "nullable": true,
-                      "description": "Specifies the active line conductors used in the circuit. - `L1_L2` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L2_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L2` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L3` - Valid when `phases` = `single_phase` in electrical configuration `star`"
-                    }
-                  }
-                },
                 "externalId": {
                   "type": "string"
                 },
@@ -13309,6 +13517,86 @@
                     }
                   },
                   "description": "Manual overrides for individual EVSE capabilities. Each property is independent. Send `force_enable` or `force_disable` to set or replace an override. Send `auto` to clear an existing override (the capability returns to automated detection). Omit a property to leave its current override unchanged."
+                },
+                "powerOptions": {
+                  "type": "object",
+                  "properties": {
+                    "maxPower": {
+                      "type": "integer",
+                      "nullable": true,
+                      "description": "Maximum power of the EVSE in W (Watts)."
+                    },
+                    "maxVoltage": {
+                      "type": "string",
+                      "enum": [
+                        "230",
+                        "380",
+                        "400",
+                        "480",
+                        "600",
+                        "120",
+                        "208",
+                        "240",
+                        "110-130",
+                        "220-240",
+                        "277"
+                      ],
+                      "nullable": true,
+                      "description": "The maximum intake (input) voltage of the EVSE. For the ac current type the output voltage is the same as this intake voltage, while for the dc current type the output voltage can differ and is exposed separately in maxOutputVoltage. The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
+                    },
+                    "maxAmperage": {
+                      "type": "number",
+                      "nullable": true
+                    },
+                    "phases": {
+                      "type": "string",
+                      "enum": [
+                        "single_phase",
+                        "three_phase",
+                        "split_phase"
+                      ],
+                      "nullable": true
+                    },
+                    "phaseRotation": {
+                      "type": "string",
+                      "enum": [
+                        "RST",
+                        "RTS",
+                        "SRT",
+                        "STR",
+                        "TRS",
+                        "TSR"
+                      ],
+                      "nullable": true,
+                      "description": "`R` stands for `L1`, </br> `S` - for `L2` </br> `T` - for `L3` </br> So for example `RST` = `L1`, `L2`, `L3`, while `RTS` = `L1`, `L3`, `L2`, etc. </br> We are deriving the connected phase from this property for single phase if connectedPhase is not provided. Please don't rely on this property anymore as this functionality will be turned of in near future. Pass the correct connectedPhase instead. If you pass both properties (connectedPhase and phaseRotation) only connectedPhase will be taken into consideration for determining the phase."
+                    },
+                    "connectedPhase": {
+                      "type": "string",
+                      "enum": [
+                        "L1",
+                        "L2",
+                        "L3",
+                        "L1_L2",
+                        "L1_L3",
+                        "L2_L3"
+                      ],
+                      "nullable": true,
+                      "description": "Specifies the active line conductors used in the circuit. - `L1_L2` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L2_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L2` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L3` - Valid when `phases` = `single_phase` in electrical configuration `star`"
+                    },
+                    "maxOutputVoltage": {
+                      "type": "integer",
+                      "minimum": 1,
+                      "maximum": 1000,
+                      "nullable": true,
+                      "description": "Maximum output voltage for DC charging, in V. Leave empty to share the input voltage via roaming connections. Only relevant for the dc current type - providing a value for any other current type is rejected with a validation error."
+                    },
+                    "efficiencyPercent": {
+                      "type": "number",
+                      "nullable": true,
+                      "description": "Stored efficiency override for a local DC EVSE. New or changed values must be numbers from 90 to 100; invalid supplied local values return 422. An unchanged numeric value, including a historical value outside this range, is accepted without rewriting storage even when switching to AC; AC responses hide the retained value. Changed values are rounded to two decimal places when stored and take effect on the next DLM cycle. Without an override, DLM uses 95% for calculations. Omission preserves the stored override. Sending powerOptions: null clears the other power options but retains any stored efficiency override; send powerOptions: {efficiencyPercent: null} to clear the override. Roaming EVSEs ignore this property."
+                    }
+                  },
+                  "description": "Set efficiencyPercent to a number from 90 to 100 only for a local DC EVSE; invalid new or changed local values return 422. An unchanged numeric value is accepted even when outside this range or when changing to AC, and its stored value is left untouched. New values are rounded to two decimal places when stored and used by the next DLM cycle; without an override DLM uses 95%. Omission preserves the stored override even when changing to AC. Sending powerOptions: null clears the other power options but retains any stored efficiency override; send powerOptions: {efficiencyPercent: null} to clear the override. Roaming EVSEs ignore this property."
                 }
               }
             }
@@ -13441,11 +13729,17 @@
                     "enabled",
                     "disabled"
                   ]
+                },
+                "externalId": {
+                  "type": "string",
+                  "maxLength": 255,
+                  "description": "An optional external identifier for integration purposes"
                 }
               },
               "required": [
                 "type"
-              ]
+              ],
+              "description": "Omit optional externalId when no identifier is available. Supplied non-string or longer-than-255-character values return 422 without creating a connector. Identifiers are not unique across connectors."
             }
           }
         }
@@ -13588,8 +13882,15 @@
                     "enabled",
                     "disabled"
                   ]
+                },
+                "externalId": {
+                  "type": "string",
+                  "maxLength": 255,
+                  "nullable": true,
+                  "description": "An optional external identifier for integration purposes"
                 }
-              }
+              },
+              "description": "Set or replace externalId, or send null or an empty string to clear it. Omission preserves the current identifier. Supplied non-string or longer-than-255-character values return 422 without changing the connector. Identifiers are not unique across connectors."
             }
           }
         }
@@ -15125,6 +15426,7 @@
                         "380",
                         "400",
                         "480",
+                        "600",
                         "120",
                         "208",
                         "240",
@@ -15256,6 +15558,7 @@
                         "380",
                         "400",
                         "480",
+                        "600",
                         "120",
                         "208",
                         "240",
@@ -15387,6 +15690,7 @@
                         "380",
                         "400",
                         "480",
+                        "600",
                         "120",
                         "208",
                         "240",
@@ -16172,6 +16476,7 @@
                     "380",
                     "400",
                     "480",
+                    "600",
                     "120",
                     "208",
                     "240",
@@ -16435,6 +16740,7 @@
                     "380",
                     "400",
                     "480",
+                    "600",
                     "120",
                     "208",
                     "240",
@@ -18149,6 +18455,171 @@
         }
       }
     },
+    {
+      "path": "/public-api/resources/cooperator-insights/v1.0",
+      "method": "GET",
+      "operationId": "cooperatorInsightsListing",
+      "summary": "CoOperator insights / listing",
+      "description": "⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. Get API insights in descending ID order. Requires a Public API token whose service admin has the Access CoOperator permission and an installed, enabled CoOperator app. Every request is rejected with `403` while CoOperator's in-process mode is not enabled for the tenant. Only insights submitted through this API are visible. An operator-level admin sees every insight of its operator, including those submitted by its partner and sub-operator admins; a partner or sub-operator admin sees only the insights submitted by admins of its own partner or sub-operator; a global admin sees all of them. Admins of any other kind, such as installation and maintenance companies, are refused with `403`. An insight submitted by a global admin is visible only to global admins. Inaccessible insight IDs are not exposed and return `404`. A `failed` insight exposes no failure details. Callers should enforce their own polling timeout because stale `pending` insights are not automatically expired.",
+      "tags": [
+        "resource / cooperator insights"
+      ],
+      "parameters": {
+        "query": {
+          "per_page": {
+            "description": "The number of items to return per page.",
+            "type": "integer",
+            "minimum": 1,
+            "maximum": 100,
+            "default": 100
+          },
+          "cursor": {
+            "description": "The cursor to fetch the next page. **Do not construct this value manually.** Use one of the following methods: - Use the value from the previous response's `links.next` to fetch the next page - Pass an empty string (e.g., `?cursor` or `?cursor=`) to initiate cursor pagination on the first page",
+            "type": "string"
+          },
+          "filter": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "state": {
+                  "type": "string",
+                  "enum": [
+                    "pending",
+                    "completed",
+                    "failed"
+                  ],
+                  "description": "Current processing state: - `pending` — The analysis is queued or in progress. - `completed` — The analysis completed and `content` is available. - `failed` — The analysis could not be completed."
+                },
+                "createdAfter": {
+                  "type": "string",
+                  "format": "date-time",
+                  "description": "Return insights created at or after this moment."
+                },
+                "createdBefore": {
+                  "type": "string",
+                  "format": "date-time",
+                  "description": "Return insights created at or before this moment."
+                }
+              }
+            }
+          }
+        }
+      },
+      "responses": {
+        "200": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/resources/cooperator-insights/v1.0",
+      "method": "POST",
+      "operationId": "cooperatorInsightCreate",
+      "summary": "CoOperator insight / create",
+      "description": "⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. Submit one question for a single, fully automatic, read-only analysis, for example \"What happened to user 123?\". CoOperator never asks a follow-up question and never waits for confirmation: it always answers with its best effort using the platform data the token's service admin can access, states any assumption it made, and reports what it could not determine. Requests for a change are analysed but never carried out. Poll the read endpoint with the returned `id` until the state is `completed` or `failed`, or subscribe to the `CoOperatorInsightChangedNotification` webhook through notifications v2.0, which delivers the insight in this same shape as soon as it leaves `pending`. The webhook reaches operator-level and global subscriptions only, see its own documentation for the recipient rule. One analysis runs per administrator at a time: a request made while the token's service admin already has a `pending` insight that can still execute is refused with `409`. Once that insight has completed or failed, a new request is accepted. Creation is not idempotent: every accepted request is a new insight, so retry only after reading the state of the one you already have. Requires a Public API token whose service admin has the Access CoOperator permission and an installed, enabled CoOperator app. Every request is rejected with `403` while CoOperator's in-process mode is not enabled for the tenant. `message` and `context` are treated as untrusted input and are not returned by the insight resource. The caller must retain its own copy. Allowance is checked when the request is accepted and an exhausted allowance returns `429`. This best-effort check reserves and refunds nothing, can permit a small overshoot from concurrent requests, and does not prevent already accepted work from completing after the allowance is exhausted.",
+      "tags": [
+        "resource / cooperator insights"
+      ],
+      "requestBody": {
+        "required": true,
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "message": {
+                  "type": "string",
+                  "minLength": 1,
+                  "maxLength": 10000,
+                  "description": "Untrusted question or analysis request. It is not returned by the insight resource, so the caller must retain its own copy."
+                },
+                "context": {
+                  "type": "object",
+                  "additionalProperties": {
+                    "oneOf": [
+                      {
+                        "type": "string",
+                        "maxLength": 1000
+                      },
+                      {
+                        "type": "number"
+                      },
+                      {
+                        "type": "boolean"
+                      }
+                    ]
+                  },
+                  "description": "Optional untrusted scalar context with property names up to 100 characters and string values up to 1000 characters. Empty strings and null values are rejected, so omit a property that has no value. It is not returned by the insight resource, so the caller must retain its own copy."
+                }
+              },
+              "required": [
+                "message"
+              ],
+              "description": "⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed."
+            }
+          }
+        }
+      },
+      "responses": {
+        "202": {
+          "description": "Accepted"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "409": {
+          "description": "The request could not be completed due to a conflict with the current state of the resource. The operation may succeed if retried."
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/resources/cooperator-insights/v1.0/{insight}",
+      "method": "GET",
+      "operationId": "cooperatorInsightRead",
+      "summary": "CoOperator insight / read",
+      "description": "⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. Get one API insight. Requires a Public API token whose service admin has the Access CoOperator permission and an installed, enabled CoOperator app. Every request is rejected with `403` while CoOperator's in-process mode is not enabled for the tenant. Only insights submitted through this API are visible. An operator-level admin sees every insight of its operator, including those submitted by its partner and sub-operator admins; a partner or sub-operator admin sees only the insights submitted by admins of its own partner or sub-operator; a global admin sees all of them. Admins of any other kind, such as installation and maintenance companies, are refused with `403`. An insight submitted by a global admin is visible only to global admins. Inaccessible insight IDs are not exposed and return `404`. A `failed` insight exposes no failure details. Callers should enforce their own polling timeout because stale `pending` insights are not automatically expired.",
+      "tags": [
+        "resource / cooperator insights"
+      ],
+      "responses": {
+        "200": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
     {
       "path": "/public-api/resources/cp-models/v1.0",
       "method": "GET",
@@ -24056,6 +24527,7 @@
                         "380",
                         "400",
                         "480",
+                        "600",
                         "120",
                         "208",
                         "240",
@@ -24662,6 +25134,31 @@
                     "dc"
                   ],
                   "description": "Filter EVSEs by current type. If 'ac', only AC EVSEs will be returned. If 'dc', only DC EVSEs will be returned. If not provided, all EVSEs will be returned."
+                },
+                "hardwareStatus": {
+                  "type": "array",
+                  "items": {
+                    "type": "string",
+                    "enum": [
+                      "available",
+                      "preparing",
+                      "charging",
+                      "suspendedEV",
+                      "suspendedEVSE",
+                      "finishing",
+                      "reserved",
+                      "unavailable",
+                      "faulted",
+                      "occupied"
+                    ],
+                    "example": "suspendedEV",
+                    "description": "EVSE hardware status: - **available**: EVSE is available for use - **preparing**: EVSE is preparing to charge (e.g., cable plugged in, awaiting authorization) - **charging**: EVSE is actively charging a vehicle - **suspendedEV**: Charging is suspended by the EV (vehicle-side pause) - **suspendedEVSE**: Charging is suspended by the EVSE (charger-side pause) - **finishing**: Charging session is finishing - **reserved**: EVSE is reserved - **unavailable**: EVSE is not available for use - **faulted**: EVSE is in a faulted state - **occupied**: EVSE is occupied"
+                  },
+                  "example": [
+                    "occupied",
+                    "suspendedEVSE"
+                  ],
+                  "description": "Filter by any of the supplied case-sensitive hardware statuses (OR). Send a one-element array for a single status. Blank array members, including `filter[hardwareStatus][]=` in the query, and a blank scalar are ignored; an all-blank array does not filter results. A nonblank scalar, unknown status or incorrectly cased status returns 422. Can be combined with chargePointId and other filters."
                 }
               }
             }
@@ -24785,78 +25282,6 @@
                   "type": "boolean",
                   "description": "When disabled, this EVSE will not be listed or counted in the Faults & connectivity loss widget or lens. The charge point will still appear for charge point-level faults (network loss, hardware faulted). Defaults to true."
                 },
-                "powerOptions": {
-                  "type": "object",
-                  "properties": {
-                    "maxOutputVoltage": {
-                      "type": "integer",
-                      "minimum": 1,
-                      "maximum": 1000,
-                      "description": "Maximum output voltage for DC charging."
-                    },
-                    "maxPower": {
-                      "type": "integer",
-                      "nullable": true,
-                      "description": "Maximum power of the EVSE in W (Watts)."
-                    },
-                    "maxVoltage": {
-                      "type": "string",
-                      "enum": [
-                        "230",
-                        "380",
-                        "400",
-                        "480",
-                        "120",
-                        "208",
-                        "240",
-                        "110-130",
-                        "220-240",
-                        "277"
-                      ],
-                      "nullable": true,
-                      "description": "The maximum intake (input) voltage of the EVSE. For the ac current type the output voltage is the same as this intake voltage, while for the dc current type the output voltage can differ and is exposed separately in maxOutputVoltage. The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
-                    },
-                    "maxAmperage": {
-                      "type": "number",
-                      "nullable": true
-                    },
-                    "phases": {
-                      "type": "string",
-                      "enum": [
-                        "single_phase",
-                        "three_phase",
-                        "split_phase"
-                      ],
-                      "nullable": true
-                    },
-                    "phaseRotation": {
-                      "type": "string",
-                      "enum": [
-                        "RST",
-                        "RTS",
-                        "SRT",
-                        "STR",
-                        "TRS",
-                        "TSR"
-                      ],
-                      "nullable": true,
-                      "description": "`R` stands for `L1`, </br> `S` - for `L2` </br> `T` - for `L3` </br> So for example `RST` = `L1`, `L2`, `L3`, while `RTS` = `L1`, `L3`, `L2`, etc. </br> We are deriving the connected phase from this property for single phase if connectedPhase is not provided. Please don't rely on this property anymore as this functionality will be turned of in near future. Pass the correct connectedPhase instead. If you pass both properties (connectedPhase and phaseRotation) only connectedPhase will be taken into consideration for determining the phase."
-                    },
-                    "connectedPhase": {
-                      "type": "string",
-                      "enum": [
-                        "L1",
-                        "L2",
-                        "L3",
-                        "L1_L2",
-                        "L1_L3",
-                        "L2_L3"
-                      ],
-                      "nullable": true,
-                      "description": "Specifies the active line conductors used in the circuit. - `L1_L2` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L2_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L2` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L3` - Valid when `phases` = `single_phase` in electrical configuration `star`"
-                    }
-                  }
-                },
                 "externalId": {
                   "type": "string"
                 },
@@ -24982,6 +25407,87 @@
                     }
                   },
                   "description": "Manual overrides for individual EVSE capabilities. Each property is independent. Send `force_enable` or `force_disable` to set or replace an override. Send `auto` to clear an existing override (the capability returns to automated detection). Omit a property to leave its current override unchanged."
+                },
+                "powerOptions": {
+                  "type": "object",
+                  "properties": {
+                    "maxPower": {
+                      "type": "integer",
+                      "nullable": true,
+                      "description": "Maximum power of the EVSE in W (Watts)."
+                    },
+                    "maxVoltage": {
+                      "type": "string",
+                      "enum": [
+                        "230",
+                        "380",
+                        "400",
+                        "480",
+                        "600",
+                        "120",
+                        "208",
+                        "240",
+                        "110-130",
+                        "220-240",
+                        "277"
+                      ],
+                      "nullable": true,
+                      "description": "The maximum intake (input) voltage of the EVSE. For the ac current type the output voltage is the same as this intake voltage, while for the dc current type the output voltage can differ and is exposed separately in maxOutputVoltage. The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
+                    },
+                    "maxAmperage": {
+                      "type": "number",
+                      "nullable": true
+                    },
+                    "phases": {
+                      "type": "string",
+                      "enum": [
+                        "single_phase",
+                        "three_phase",
+                        "split_phase"
+                      ],
+                      "nullable": true
+                    },
+                    "phaseRotation": {
+                      "type": "string",
+                      "enum": [
+                        "RST",
+                        "RTS",
+                        "SRT",
+                        "STR",
+                        "TRS",
+                        "TSR"
+                      ],
+                      "nullable": true,
+                      "description": "`R` stands for `L1`, </br> `S` - for `L2` </br> `T` - for `L3` </br> So for example `RST` = `L1`, `L2`, `L3`, while `RTS` = `L1`, `L3`, `L2`, etc. </br> We are deriving the connected phase from this property for single phase if connectedPhase is not provided. Please don't rely on this property anymore as this functionality will be turned of in near future. Pass the correct connectedPhase instead. If you pass both properties (connectedPhase and phaseRotation) only connectedPhase will be taken into consideration for determining the phase."
+                    },
+                    "connectedPhase": {
+                      "type": "string",
+                      "enum": [
+                        "L1",
+                        "L2",
+                        "L3",
+                        "L1_L2",
+                        "L1_L3",
+                        "L2_L3"
+                      ],
+                      "nullable": true,
+                      "description": "Specifies the active line conductors used in the circuit. - `L1_L2` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L2_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L2` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L3` - Valid when `phases` = `single_phase` in electrical configuration `star`"
+                    },
+                    "maxOutputVoltage": {
+                      "type": "integer",
+                      "minimum": 1,
+                      "maximum": 1000,
+                      "nullable": true,
+                      "description": "Maximum output voltage for DC charging, in V. Leave empty to share the input voltage via roaming connections. Only relevant for the dc current type - providing a value for any other current type is rejected with a validation error."
+                    },
+                    "efficiencyPercent": {
+                      "type": "number",
+                      "minimum": 90,
+                      "maximum": 100,
+                      "description": "Stored efficiency override for a local DC EVSE. Supply a number from 90 to 100; invalid supplied local values return 422. Values are rounded to two decimal places when stored and take effect on the next DLM cycle. Without an override, DLM uses 95% for calculations. Omit this property for no override. Roaming EVSEs ignore this property."
+                    }
+                  },
+                  "description": "Optional efficiencyPercent sets a stored override for a local DC EVSE. Supply a number from 90 to 100; invalid supplied local values return 422. Values are rounded to two decimal places when stored and applied on the next DLM cycle; without an override DLM uses 95%. Roaming EVSEs ignore this property. Omit the property for no override."
                 }
               },
               "required": [
@@ -25174,78 +25680,6 @@
                   "type": "boolean",
                   "description": "When disabled, this EVSE will not be listed or counted in the Faults & connectivity loss widget or lens. The charge point will still appear for charge point-level faults (network loss, hardware faulted). Defaults to true."
                 },
-                "powerOptions": {
-                  "type": "object",
-                  "properties": {
-                    "maxOutputVoltage": {
-                      "type": "integer",
-                      "minimum": 1,
-                      "maximum": 1000,
-                      "description": "Maximum output voltage for DC charging."
-                    },
-                    "maxPower": {
-                      "type": "integer",
-                      "nullable": true,
-                      "description": "Maximum power of the EVSE in W (Watts)."
-                    },
-                    "maxVoltage": {
-                      "type": "string",
-                      "enum": [
-                        "230",
-                        "380",
-                        "400",
-                        "480",
-                        "120",
-                        "208",
-                        "240",
-                        "110-130",
-                        "220-240",
-                        "277"
-                      ],
-                      "nullable": true,
-                      "description": "The maximum intake (input) voltage of the EVSE. For the ac current type the output voltage is the same as this intake voltage, while for the dc current type the output voltage can differ and is exposed separately in maxOutputVoltage. The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
-                    },
-                    "maxAmperage": {
-                      "type": "number",
-                      "nullable": true
-                    },
-                    "phases": {
-                      "type": "string",
-                      "enum": [
-                        "single_phase",
-                        "three_phase",
-                        "split_phase"
-                      ],
-                      "nullable": true
-                    },
-                    "phaseRotation": {
-                      "type": "string",
-                      "enum": [
-                        "RST",
-                        "RTS",
-                        "SRT",
-                        "STR",
-                        "TRS",
-                        "TSR"
-                      ],
-                      "nullable": true,
-                      "description": "`R` stands for `L1`, </br> `S` - for `L2` </br> `T` - for `L3` </br> So for example `RST` = `L1`, `L2`, `L3`, while `RTS` = `L1`, `L3`, `L2`, etc. </br> We are deriving the connected phase from this property for single phase if connectedPhase is not provided. Please don't rely on this property anymore as this functionality will be turned of in near future. Pass the correct connectedPhase instead. If you pass both properties (connectedPhase and phaseRotation) only connectedPhase will be taken into consideration for determining the phase."
-                    },
-                    "connectedPhase": {
-                      "type": "string",
-                      "enum": [
-                        "L1",
-                        "L2",
-                        "L3",
-                        "L1_L2",
-                        "L1_L3",
-                        "L2_L3"
-                      ],
-                      "nullable": true,
-                      "description": "Specifies the active line conductors used in the circuit. - `L1_L2` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L2_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L2` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L3` - Valid when `phases` = `single_phase` in electrical configuration `star`"
-                    }
-                  }
-                },
                 "externalId": {
                   "type": "string"
                 },
@@ -25371,6 +25805,86 @@
                     }
                   },
                   "description": "Manual overrides for individual EVSE capabilities. Each property is independent. Send `force_enable` or `force_disable` to set or replace an override. Send `auto` to clear an existing override (the capability returns to automated detection). Omit a property to leave its current override unchanged."
+                },
+                "powerOptions": {
+                  "type": "object",
+                  "properties": {
+                    "maxPower": {
+                      "type": "integer",
+                      "nullable": true,
+                      "description": "Maximum power of the EVSE in W (Watts)."
+                    },
+                    "maxVoltage": {
+                      "type": "string",
+                      "enum": [
+                        "230",
+                        "380",
+                        "400",
+                        "480",
+                        "600",
+                        "120",
+                        "208",
+                        "240",
+                        "110-130",
+                        "220-240",
+                        "277"
+                      ],
+                      "nullable": true,
+                      "description": "The maximum intake (input) voltage of the EVSE. For the ac current type the output voltage is the same as this intake voltage, while for the dc current type the output voltage can differ and is exposed separately in maxOutputVoltage. The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
+                    },
+                    "maxAmperage": {
+                      "type": "number",
+                      "nullable": true
+                    },
+                    "phases": {
+                      "type": "string",
+                      "enum": [
+                        "single_phase",
+                        "three_phase",
+                        "split_phase"
+                      ],
+                      "nullable": true
+                    },
+                    "phaseRotation": {
+                      "type": "string",
+                      "enum": [
+                        "RST",
+                        "RTS",
+                        "SRT",
+                        "STR",
+                        "TRS",
+                        "TSR"
+                      ],
+                      "nullable": true,
+                      "description": "`R` stands for `L1`, </br> `S` - for `L2` </br> `T` - for `L3` </br> So for example `RST` = `L1`, `L2`, `L3`, while `RTS` = `L1`, `L3`, `L2`, etc. </br> We are deriving the connected phase from this property for single phase if connectedPhase is not provided. Please don't rely on this property anymore as this functionality will be turned of in near future. Pass the correct connectedPhase instead. If you pass both properties (connectedPhase and phaseRotation) only connectedPhase will be taken into consideration for determining the phase."
+                    },
+                    "connectedPhase": {
+                      "type": "string",
+                      "enum": [
+                        "L1",
+                        "L2",
+                        "L3",
+                        "L1_L2",
+                        "L1_L3",
+                        "L2_L3"
+                      ],
+                      "nullable": true,
+                      "description": "Specifies the active line conductors used in the circuit. - `L1_L2` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L2_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1_L3` - Valid when `phases` = `split_phase` in electrical configuration `star` or `phases` = `single_phase` in electrical configuration `delta` - `L1` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L2` - Valid when `phases` = `single_phase` in electrical configuration `star` - `L3` - Valid when `phases` = `single_phase` in electrical configuration `star`"
+                    },
+                    "maxOutputVoltage": {
+                      "type": "integer",
+                      "minimum": 1,
+                      "maximum": 1000,
+                      "nullable": true,
+                      "description": "Maximum output voltage for DC charging, in V. Leave empty to share the input voltage via roaming connections. Only relevant for the dc current type - providing a value for any other current type is rejected with a validation error."
+                    },
+                    "efficiencyPercent": {
+                      "type": "number",
+                      "nullable": true,
+                      "description": "Stored efficiency override for a local DC EVSE. New or changed values must be numbers from 90 to 100; invalid supplied local values return 422. An unchanged numeric value, including a historical value outside this range, is accepted without rewriting storage even when switching to AC; AC responses hide the retained value. Changed values are rounded to two decimal places when stored and take effect on the next DLM cycle. Without an override, DLM uses 95% for calculations. Omission preserves the stored override. Sending powerOptions: null clears the other power options but retains any stored efficiency override; send powerOptions: {efficiencyPercent: null} to clear the override. Roaming EVSEs ignore this property."
+                    }
+                  },
+                  "description": "Set efficiencyPercent to a number from 90 to 100 only for a local DC EVSE; invalid new or changed local values return 422. An unchanged numeric value is accepted even when outside this range or when changing to AC, and its stored value is left untouched. New values are rounded to two decimal places when stored and used by the next DLM cycle; without an override DLM uses 95%. Omission preserves the stored override even when changing to AC. Sending powerOptions: null clears the other power options but retains any stored efficiency override; send powerOptions: {efficiencyPercent: null} to clear the override. Roaming EVSEs ignore this property."
                 }
               }
             }
@@ -32211,13 +32725,13 @@
       "method": "GET",
       "operationId": "locationRead",
       "summary": "Location / Read",
-      "description": "Get a location",
+      "description": "Get a location. Full access returns the existing location representation. If full access is unavailable, a partner or sub-operator with location view permission can read a restricted public representation when the location has at least one non-deleted public charge point or roaming charge point through a non-deleted charging zone. A roaming charge point qualifies when it has a current EVSE linked to a roaming EVSE. Full access takes precedence at mixed locations. Neither the location's enabled status nor a current charge point's enabled status limits this restricted read. Deleted charge points and charging zones do not qualify. The restricted representation exposes only `id`, `operatorId`, `roamingOperatorId`, `isRoaming`, `name`, `description`, `shortDescription`, `additionalDescription`, `geoposition`, `address`, `streetAddress`, `city`, `region` or `state` according to country, `country`, `postCode`, `timezone`, `workingHours`, `facilities`, `accessMethods`, `accessibilityType` and `lastUpdatedAt` when those properties are present under the existing response rules. `accessibilityType` is always present; invalid or missing stored values use `free_publicly_accessible` in this representation. Requested `include[]=locationImage` and `include[]=images` may add `locationImage` and `images`; other requested includes are ignored. Restricted `workingHours` contains only `isAlwaysOpen` and, when the location is not always open, `hours`. It excludes user-group IDs and administrative charging controls. In particular, the restricted representation never exposes `status`, `externalId`, `tags`, `roaming`, `parkingType`, `paymentOptions`, `acceptedPaymentBrands`, `createdAt`, `averagePrice`, `locationPin`, `chargingZones`, `partnerIds`, `externalAppData` or `notes`. Newly added full-response fields are not automatically public. This exception affects only this v2 detail read: location listings, v1, admin access and mutations retain their existing permissions and output. Site managers do not receive the restricted exception, even for unmanaged public locations; operators and reimbursement-only accounts do not receive it either. Missing or deleted locations return 404; existing locations without qualifying current charge points, location view permission, or the required operator scope return 403.",
       "tags": [
         "resource / locations"
       ],
       "responses": {
         "200": {
-          "description": "Location returned"
+          "description": "Full or restricted public location returned"
         },
         "401": {
           "description": "Access token is missing or invalid"
@@ -32228,6 +32742,9 @@
         "404": {
           "description": "The record is not found"
         },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
         "429": {
           "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
         }
@@ -39721,7 +40238,7 @@
       "method": "POST",
       "operationId": "partnerInviteCreateV2_0",
       "summary": "Partner invite / Create",
-      "description": "Create a partner invite. Reimbursement coverage of specific RFIDs and vehicles (`allow`) can be declared here only when the invited email address resolves to an existing user of the partner's operator — the listed RFIDs and vehicles must belong to that user. When no such user exists yet, coverage of specific entities is rejected with a validation error; create the invite without it and declare the covered set via the update endpoint once the invite is accepted. **Experimental endpoint — not yet a stable contract.** `partner-invites/v2.0` ships as **experimental / beta**. While experimental, its schema and behaviour may change **without a version bump — including breaking changes within `v2.0` itself**. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.",
+      "description": "Create a partner invite. Reimbursement coverage of specific RFIDs and vehicles (`allow`) can be declared here only when the invited email address resolves to an existing user of the partner's operator, since the listed entities are validated against that user — listed RFIDs must belong to the invite's partner and must either belong to that user or have no owner, and listed vehicles must belong to the invite's partner. When no such user exists yet, coverage of specific entities is rejected with a validation error; create the invite without it and declare the covered set via the update endpoint once the invite is accepted. Declaring coverage of specific entities also assigns them to the invited user: listed RFIDs with no owner get that user as their owner, and that user is added to the users of listed vehicles they are not yet a user of. This happens when the invite is accepted if it is still pending, or as part of the write itself when the invite is already accepted — including on the update endpoint. **Experimental endpoint — not yet a stable contract.** `partner-invites/v2.0` ships as **experimental / beta**. While experimental, its schema and behaviour may change **without a version bump — including breaking changes within `v2.0` itself**. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.",
       "tags": [
         "resource / partner invites"
       ],
@@ -39850,7 +40367,7 @@
                               "items": {
                                 "type": "integer"
                               },
-                              "description": "The covered set of RFID IDs. Required and must be non-empty when type is `allow`; each must belong to the invited user. Listed RFIDs that are not yet attached are attached automatically, and attached RFIDs left off the list are detached. Omitted when type is `none`."
+                              "description": "The covered set of RFID IDs. Required and must be non-empty when type is `allow`; each must belong to the invite's partner, and must either belong to the invited user or have no owner. Listed RFIDs that are not yet attached are attached automatically, and attached RFIDs left off the list are detached. A listed RFID with no owner is assigned to the invited user when the invite is accepted if it is still pending, or as part of the write itself when the invite is already accepted. Omitted when type is `none`."
                             }
                           },
                           "required": [
@@ -39874,7 +40391,7 @@
                               "items": {
                                 "type": "integer"
                               },
-                              "description": "The covered set of vehicle IDs. Required and must be non-empty when type is `allow`; each must belong to the invited user. Listed vehicles that are not yet attached are attached automatically, and attached vehicles left off the list are detached. Omitted when type is `none`."
+                              "description": "The covered set of vehicle IDs. Required and must be non-empty when type is `allow`; each must belong to the invite's partner. Listed vehicles that are not yet attached are attached automatically, and attached vehicles left off the list are detached. The invited user is added to the users of a listed vehicle they are not yet a user of when the invite is accepted if it is still pending, or as part of the write itself when the invite is already accepted. Omitted when type is `none`."
                             }
                           },
                           "required": [
@@ -39883,7 +40400,7 @@
                           "description": "Reimbursement coverage for the invite's vehicles."
                         }
                       },
-                      "description": "Which of the invite's RFIDs and vehicles are covered by reimbursement. On read this reports the current covered set. On write the submitted list declares the covered set: listed RFIDs/vehicles are attached automatically (they must belong to the invited user), and attached entities left off the list are detached."
+                      "description": "Which of the invite's RFIDs and vehicles are covered by reimbursement. On read this reports the current covered set. On write the submitted list declares the covered set: listed RFIDs/vehicles are attached automatically (RFIDs must belong to the invite's partner and must either belong to the invited user or have no owner, and vehicles must belong to the invite's partner), and attached entities left off the list are detached. Listed RFIDs that have no owner are assigned to the invited user, and the invited user is added to the users of listed vehicles they are not yet a user of — when the invite is accepted if it is still pending, or as part of the write itself when the invite is already accepted."
                     }
                   },
                   "description": "Home-charging reimbursement settings for the invite. Ignored when home-charging reimbursement is disabled."
@@ -39990,7 +40507,7 @@
       "method": "PATCH",
       "operationId": "partnerInviteUpdateV2_0",
       "summary": "Partner invite / Update",
-      "description": "Update a partner invite. **Experimental endpoint — not yet a stable contract.** `partner-invites/v2.0` ships as **experimental / beta**. While experimental, its schema and behaviour may change **without a version bump — including breaking changes within `v2.0` itself**. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.",
+      "description": "Update a partner invite. Declaring reimbursement coverage of specific RFIDs and vehicles (`allow`) also assigns them to the invited user: listed RFIDs with no owner get that user as their owner, and that user is added to the users of listed vehicles they are not yet a user of. When the invite is still pending this happens once it is accepted; when the invite is already accepted it happens as part of this request. Listed RFIDs must belong to the invite's partner and must either belong to the invited user or have no owner, and listed vehicles must belong to the invite's partner. **Experimental endpoint — not yet a stable contract.** `partner-invites/v2.0` ships as **experimental / beta**. While experimental, its schema and behaviour may change **without a version bump — including breaking changes within `v2.0` itself**. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.",
       "tags": [
         "resource / partner invites"
       ],
@@ -40049,7 +40566,7 @@
                               "items": {
                                 "type": "integer"
                               },
-                              "description": "The covered set of RFID IDs. Required and must be non-empty when type is `allow`; each must belong to the invited user. Listed RFIDs that are not yet attached are attached automatically, and attached RFIDs left off the list are detached. Omitted when type is `none`."
+                              "description": "The covered set of RFID IDs. Required and must be non-empty when type is `allow`; each must belong to the invite's partner, and must either belong to the invited user or have no owner. Listed RFIDs that are not yet attached are attached automatically, and attached RFIDs left off the list are detached. A listed RFID with no owner is assigned to the invited user when the invite is accepted if it is still pending, or as part of the write itself when the invite is already accepted. Omitted when type is `none`."
                             }
                           },
                           "required": [
@@ -40073,7 +40590,7 @@
                               "items": {
                                 "type": "integer"
                               },
-                              "description": "The covered set of vehicle IDs. Required and must be non-empty when type is `allow`; each must belong to the invited user. Listed vehicles that are not yet attached are attached automatically, and attached vehicles left off the list are detached. Omitted when type is `none`."
+                              "description": "The covered set of vehicle IDs. Required and must be non-empty when type is `allow`; each must belong to the invite's partner. Listed vehicles that are not yet attached are attached automatically, and attached vehicles left off the list are detached. The invited user is added to the users of a listed vehicle they are not yet a user of when the invite is accepted if it is still pending, or as part of the write itself when the invite is already accepted. Omitted when type is `none`."
                             }
                           },
                           "required": [
@@ -40082,7 +40599,7 @@
                           "description": "Reimbursement coverage for the invite's vehicles."
                         }
                       },
-                      "description": "Which of the invite's RFIDs and vehicles are covered by reimbursement. On read this reports the current covered set. On write the submitted list declares the covered set: listed RFIDs/vehicles are attached automatically (they must belong to the invited user), and attached entities left off the list are detached."
+                      "description": "Which of the invite's RFIDs and vehicles are covered by reimbursement. On read this reports the current covered set. On write the submitted list declares the covered set: listed RFIDs/vehicles are attached automatically (RFIDs must belong to the invite's partner and must either belong to the invited user or have no owner, and vehicles must belong to the invite's partner), and attached entities left off the list are detached. Listed RFIDs that have no owner are assigned to the invited user, and the invited user is added to the users of listed vehicles they are not yet a user of — when the invite is accepted if it is still pending, or as part of the write itself when the invite is already accepted."
                     }
                   },
                   "description": "Home-charging reimbursement settings for the invite. Omit the object to leave every reimbursement setting unchanged. Ignored when home-charging reimbursement is disabled."
@@ -40460,6 +40977,7 @@
                   "type": "string",
                   "enum": [
                     "electricity-tax-reimbursement",
+                    "home-charging-reimbursement",
                     "private-evse-access-fee",
                     "session-cpo"
                   ],
@@ -40504,6 +41022,11 @@
                   "type": "string",
                   "format": "date-time",
                   "description": "ISO 8601 formatted date. Lists only the revenue records that were last updated on and before this datetime"
+                },
+                "customFields": {
+                  "type": "object",
+                  "additionalProperties": true,
+                  "description": "Filter a resource listing by administrator-defined custom fields using literal dotted keys such as `filter[customFields.reference]=INV-42`, not nested `filter[customFields][reference]` keys. Text, email and URL fields accept a single string and use case- and accent-insensitive substring matching; `%`, `_` and backslashes are matched literally. Boolean fields accept `true`, `false`, `1` or `0` as strings, or boolean and integer equivalents. Number, date and date-time fields accept inclusive `filter[customFields.<identifier>][from]` and/or `filter[customFields.<identifier>][to]` bounds, including one-sided ranges. Number bounds are decimal strings from `-99999999999999.999999` to `99999999999999.999999` with at most six fractional places, compared without rounding. Dates use `YYYY-MM-DD` calendar dates; date-times use ISO 8601, with offsets normalized to UTC and no offset interpreted as UTC. Long text and JSON fields are not filterable. Custom-field criteria combine with each other and the resource's other filters using AND. Empty criteria have no effect. Malformed values for usable fields return a property-bound `422` validation error. See each listing operation for how it handles unsupported nonempty criteria."
                 }
               }
             }
@@ -40525,11 +41048,17 @@
         "200": {
           "description": "Success"
         },
+        "400": {
+          "description": "Bad Request"
+        },
         "401": {
           "description": "Access token is missing or invalid"
         },
         "403": {
           "description": "You do not have permission to perform the action"
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
         }
       }
     },
@@ -43381,7 +43910,8 @@
                     "discount": {
                       "type": "number",
                       "format": "decimal",
-                      "nullable": true
+                      "nullable": true,
+                      "description": "The current discount. An active or scheduled discount change can replace this value when it starts or ends; see the partner's discount changes."
                     }
                   }
                 },
@@ -44442,7 +44972,8 @@
                         "discount": {
                           "type": "number",
                           "format": "decimal",
-                          "nullable": true
+                          "nullable": true,
+                          "description": "The current discount. An active or scheduled discount change can replace this value when it starts or ends; see the partner's discount changes."
                         }
                       }
                     },
@@ -44880,6 +45411,343 @@
         }
       }
     },
+    {
+      "path": "/public-api/resources/partners/v2.0/{partner}/discount-changes",
+      "method": "GET",
+      "operationId": "partnerDiscountChangesListing",
+      "summary": "Partner discount changes / Listing",
+      "description": "⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v2.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. List the partner’s discount schedule history, including when corporate billing is disabled. Results use cursor pagination, newest ID first, with a default and maximum page size of 100. Filters are inclusive and ignore unfilled values. Use updatedAfter and updatedBefore to poll both manual and automatic changes. **Required permission:** `Partners.update` on the visible parent partner. Missing, out-of-scope or wrong-parent identifiers return 404; a visible partner without edit permission returns 403.",
+      "tags": [
+        "resource / partners"
+      ],
+      "parameters": {
+        "query": {
+          "filter": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "status": {
+                  "oneOf": [
+                    {
+                      "type": "string",
+                      "enum": [
+                        "scheduled",
+                        "active",
+                        "completed",
+                        "cancelled",
+                        "failed"
+                      ],
+                      "description": "Discount change lifecycle state: * `scheduled` — Waiting for its start boundary. * `active` — The limited change has started and awaits its end. * `completed` — The change has finished, or its permanent rate has been applied. * `cancelled` — The change was cancelled without applying its future boundary. * `failed` — Applying a scheduled discount boundary failed."
+                    },
+                    {
+                      "type": "string",
+                      "minLength": 0,
+                      "maxLength": 0
+                    },
+                    {
+                      "type": "array",
+                      "items": {
+                        "oneOf": [
+                          {
+                            "type": "string",
+                            "enum": [
+                              "scheduled",
+                              "active",
+                              "completed",
+                              "cancelled",
+                              "failed"
+                            ],
+                            "description": "Discount change lifecycle state: * `scheduled` — Waiting for its start boundary. * `active` — The limited change has started and awaits its end. * `completed` — The change has finished, or its permanent rate has been applied. * `cancelled` — The change was cancelled without applying its future boundary. * `failed` — Applying a scheduled discount boundary failed."
+                          },
+                          {
+                            "type": "string",
+                            "minLength": 0,
+                            "maxLength": 0
+                          }
+                        ]
+                      }
+                    }
+                  ],
+                  "description": "Filter by one status or an array of statuses (for example, filter[status][0]=scheduled&filter[status][1]=active). Empty values, including empty array elements, are ignored. An array containing only empty elements applies no status filter."
+                },
+                "startsAfter": {
+                  "oneOf": [
+                    {
+                      "type": "string",
+                      "format": "date-time"
+                    },
+                    {
+                      "type": "string",
+                      "minLength": 0,
+                      "maxLength": 0
+                    }
+                  ],
+                  "description": "Include changes starting on or after this ISO 8601 timestamp, inclusively. Empty values are ignored."
+                },
+                "startsBefore": {
+                  "oneOf": [
+                    {
+                      "type": "string",
+                      "format": "date-time"
+                    },
+                    {
+                      "type": "string",
+                      "minLength": 0,
+                      "maxLength": 0
+                    }
+                  ],
+                  "description": "Include changes starting on or before this ISO 8601 timestamp, inclusively. Empty values are ignored."
+                },
+                "updatedAfter": {
+                  "oneOf": [
+                    {
+                      "type": "string",
+                      "format": "date-time"
+                    },
+                    {
+                      "type": "string",
+                      "minLength": 0,
+                      "maxLength": 0
+                    }
+                  ],
+                  "description": "Include changes updated on or after this ISO 8601 timestamp, inclusively, by an administrator or automatically. Uses update time, not creation time. Empty values are ignored."
+                },
+                "updatedBefore": {
+                  "oneOf": [
+                    {
+                      "type": "string",
+                      "format": "date-time"
+                    },
+                    {
+                      "type": "string",
+                      "minLength": 0,
+                      "maxLength": 0
+                    }
+                  ],
+                  "description": "Include changes updated on or before this ISO 8601 timestamp, inclusively. Empty values are ignored."
+                }
+              }
+            }
+          },
+          "per_page": {
+            "description": "The number of items to return per page.",
+            "type": "integer",
+            "minimum": 1,
+            "maximum": 100,
+            "default": 100
+          },
+          "cursor": {
+            "description": "The cursor to fetch the next page. **Do not construct this value manually.** Use one of the following methods: - Use the value from the previous response's `links.next` to fetch the next page - Pass an empty string (e.g., `?cursor` or `?cursor=`) to initiate cursor pagination on the first page",
+            "type": "string"
+          }
+        }
+      },
+      "responses": {
+        "200": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/resources/partners/v2.0/{partner}/discount-changes",
+      "method": "POST",
+      "operationId": "partnerDiscountChangeCreate",
+      "summary": "Partner discount change / Create",
+      "description": "⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v2.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. Create a future scheduled discount change for a partner with corporate billing enabled. Invalid fields or conditional revert combinations return 422 with API field names. Overlapping periods return 409 with message `Another scheduled discount change already covers this period.` Disabled corporate billing returns 409. The schedule does not change discounts captured for existing sessions. **Required permission:** `Partners.update` on the visible parent partner. Missing, out-of-scope or wrong-parent identifiers return 404; a visible partner without edit permission returns 403.",
+      "tags": [
+        "resource / partners"
+      ],
+      "requestBody": {
+        "required": true,
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "discount": {
+                  "type": "number",
+                  "minimum": 0,
+                  "maximum": 100,
+                  "example": 12.5,
+                  "description": "Discount percentage, with at most two decimal places. Must be a JSON number, not a string."
+                },
+                "startsAt": {
+                  "type": "string",
+                  "format": "date-time",
+                  "example": "2027-01-01T00:00:00Z",
+                  "description": "Start timestamp. Requests must use a valid ISO 8601 timestamp with an explicit timezone or offset and minute precision (zero seconds and zero fractional seconds). Values are converted to UTC; responses use UTC."
+                },
+                "endsAt": {
+                  "type": "string",
+                  "format": "date-time",
+                  "example": "2027-02-01T00:00:00Z",
+                  "description": "End timestamp for a limited change. Requests require an explicit timezone or offset and minute precision (zero seconds and zero fractional seconds). Responses use UTC and may include seconds when ended early. Omitted for permanent changes."
+                },
+                "revertDiscount": {
+                  "type": "number",
+                  "minimum": 0,
+                  "maximum": 100,
+                  "example": 0,
+                  "description": "Discount percentage to apply when the limited change ends, with at most two decimal places. Must be a JSON number, not a string. Required when creating a limited change; omitted for permanent changes. May be omitted in incomplete historical records."
+                },
+                "note": {
+                  "type": "string",
+                  "maxLength": 16000,
+                  "description": "Optional note. Omitted in responses when empty."
+                }
+              },
+              "required": [
+                "discount",
+                "startsAt"
+              ],
+              "description": "Create a scheduled change with a future start. For a limited change, endsAt must be after startsAt and revertDiscount is required. For a permanent change, omit both endsAt and revertDiscount. Optional properties cannot be null. Periods must not overlap; adjacent periods are allowed. A permanent change represents a point in the schedule, not an indefinite occupied period."
+            }
+          }
+        }
+      },
+      "responses": {
+        "201": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "409": {
+          "description": "The request could not be completed due to a conflict with the current state of the resource. The operation may succeed if retried."
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/resources/partners/v2.0/{partner}/discount-changes/{discountChange}",
+      "method": "GET",
+      "operationId": "partnerDiscountChangeRead",
+      "summary": "Partner discount change / Read",
+      "description": "⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v2.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. Read one discount change belonging to the visible partner, including historical changes when corporate billing is disabled. Optional values are omitted, not null. Failure metadata is omitted as a whole when historical required metadata is incomplete. **Required permission:** `Partners.update` on the visible parent partner. Missing, out-of-scope or wrong-parent identifiers return 404; a visible partner without edit permission returns 403.",
+      "tags": [
+        "resource / partners"
+      ],
+      "responses": {
+        "200": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/resources/partners/v2.0/{partner}/discount-changes/{discountChange}",
+      "method": "PATCH",
+      "operationId": "partnerDiscountChangeUpdate",
+      "summary": "Partner discount change / Update",
+      "description": "⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v2.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. Partially edit a scheduled or active change under the current stored state. Omitted properties are preserved; only endsAt and note can be cleared with null. Unchanged active start and discount values are accepted. An empty or semantically identical edit leaves timestamps, actor, reason and audit unchanged, even when a scheduled start is due but not processed. Effective edits record the administrator and clear the automatic reason. Invalid supplied fields, conditional revert combinations and clearing an active end return 422 with API field names. For effective edits, an invalid startsAt or endsAt supplied in the request returns 422; when only an omitted stored timestamp blocks the edit, the response is 409 without field-validation errors. If both supplied and omitted timestamps fail validation, the supplied-field errors return 422. Disabled billing, terminal states and changed active start or discount return 409. Overlap returns 409 with message `Another scheduled discount change already covers this period.` **Required permission:** `Partners.update` on the visible parent partner. Missing, out-of-scope or wrong-parent identifiers return 404; a visible partner without edit permission returns 403.",
+      "tags": [
+        "resource / partners"
+      ],
+      "requestBody": {
+        "required": true,
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "discount": {
+                  "type": "number",
+                  "minimum": 0,
+                  "maximum": 100,
+                  "example": 12.5,
+                  "description": "Discount percentage, with at most two decimal places. Must be a JSON number, not a string."
+                },
+                "startsAt": {
+                  "type": "string",
+                  "format": "date-time",
+                  "example": "2027-01-01T00:00:00Z",
+                  "description": "Start timestamp. Requests must use a valid ISO 8601 timestamp with an explicit timezone or offset and minute precision (zero seconds and zero fractional seconds). Values are converted to UTC; responses use UTC."
+                },
+                "endsAt": {
+                  "type": "string",
+                  "format": "date-time",
+                  "example": "2027-02-01T00:00:00Z",
+                  "description": "End timestamp for a limited change. Requests require an explicit timezone or offset and minute precision (zero seconds and zero fractional seconds). Responses use UTC and may include seconds when ended early. Omitted for permanent changes."
+                },
+                "revertDiscount": {
+                  "type": "number",
+                  "minimum": 0,
+                  "maximum": 100,
+                  "example": 0,
+                  "description": "Discount percentage to apply when the limited change ends, with at most two decimal places. Must be a JSON number, not a string. Required when creating a limited change; omitted for permanent changes. May be omitted in incomplete historical records."
+                },
+                "note": {
+                  "type": "string",
+                  "maxLength": 16000,
+                  "description": "Optional note. Omitted in responses when empty."
+                }
+              },
+              "description": "Partial edit of a scheduled or active change. Omission preserves each stored value. Only endsAt and note accept explicit null. A revertDiscount without an effective end is invalid. Active startsAt and discount cannot change, but numerically identical percentages and equivalent UTC start instants are accepted. Empty or semantically identical edits preserve timestamps, actor, reason and audit history, including due-but-unprocessed scheduled changes. Malformed input and prohibited combinations remain invalid. Effective scheduled edits require a future start and validate the entire resulting period. An invalid supplied startsAt or endsAt returns 422 with that API field's validation errors; an edit blocked only by an omitted stored timestamp returns 409 without field-validation errors. Supplied-field validation errors take precedence when both supplied and omitted timestamps are invalid. Terminal states and disabled corporate billing reject even a no-op. Effective edits record the administrator and clear the automatic reason."
+            }
+          }
+        }
+      },
+      "responses": {
+        "200": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "409": {
+          "description": "The request could not be completed due to a conflict with the current state of the resource. The operation may succeed if retried."
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
     {
       "path": "/public-api/resources/partners/v2.0/{partner}/notes",
       "method": "GET",
@@ -50885,6 +51753,15 @@
             "schema": {
               "type": "object",
               "properties": {
+                "type": {
+                  "type": "string",
+                  "enum": [
+                    "user",
+                    "partner"
+                  ],
+                  "example": "user",
+                  "description": "The kind of aggregate a reimbursement report represents: - **user**: The report aggregates the records owed to a single beneficiary user. - **partner**: The report aggregates the records owed by a single payer partner contract."
+                },
                 "reimbursementType": {
                   "type": "string",
                   "enum": [
@@ -74007,7 +74884,7 @@
   ],
   "info": {
     "title": "Public API",
-    "version": "3.257.2",
+    "version": "3.258.0",
     "description": "The Public API provides server-to-server integration capabilities for your EV charging platform.\n\n**Authentication.** Existing integrations continue to work unchanged — long-lived UUID admin tokens are sent in `Authorization: Bearer ...` with no exchange required. Two security schemes are documented for OpenAPI client tooling, both resulting in the same Bearer header at the wire level:\n   - `bearerAuth` — the token in the `Authorization: Bearer ...` header is either a long-lived UUID admin token (issued via the admin UI, used directly) or a short-lived access token previously obtained via OAuth.\n   - `oauth2ClientCredentials` - a `client_id` / `client_secret` pair should be exchanged for a short-lived access token at `/public-api/oauth/token` per RFC 6749 Section 4.4 (Client Credentials Grant), and the short-lived token should be used in the `Authorization: Bearer ...` header. The OAuth `client_secret` itself cannot be sent directly as a bearer token — it must be exchanged first.\n"
   },
   "servers": [
@@ -74021,18 +74898,18 @@
       }
     }
   ],
-  "buildTimestamp": "2026-10-05T10:14:39.537Z",
+  "buildTimestamp": "2026-10-06T08:04:45.296Z",
   "stats": {
-    "totalEndpoints": 666,
-    "originalSize": 6403121,
-    "optimizedSize": 1774310,
-    "reductionPercent": 72.29,
-    "buildDuration": 2675,
+    "totalEndpoints": 679,
+    "originalSize": 6525064,
+    "optimizedSize": 1829203,
+    "reductionPercent": 71.97,
+    "buildDuration": 1693,
     "responseSchemas": {
-      "total": 666,
-      "withSchemas": 666,
-      "totalSchemaSize": 3687990,
-      "averageSchemaSize": 5538
+      "total": 679,
+      "withSchemas": 679,
+      "totalSchemaSize": 3739771,
+      "averageSchemaSize": 5508
     }
   }
 }