@ampeco/public-api-mcp 3.247.2 → 3.248.0

package/dist/generated/endpoints.json

@@ -3866,7 +3866,7 @@
       "method": "POST",
       "operationId": "partnerInvoiceIssueCreditNote",
       "summary": "Partner invoice / Issue credit note",
-      "description": "Issue a full credit note cancelling the given partner invoice. The credit note copies the original's seller, buyer, currency and payment terms, negates every line item, is marked paid, and references the cancelled invoice via `referenceId`. Only invoices generated through the built-in B2B invoice integration are eligible, and only one credit note may exist per invoice. Issuing returns the linked settlement report to `ready_to_invoice`. Partial credit notes are not supported. A `409` means the invoice is permanently ineligible and the request will not succeed on retry. It is returned when the invoice already has a credit note, when the target is itself a credit note, or when the invoice was not generated through the built-in B2B invoice integration.",
+      "description": "Issue a full credit note cancelling the given partner invoice. The credit note copies the original's seller, buyer, currency and payment terms, negates every line item, is marked paid, and references the cancelled invoice via `referenceId`. Only one credit note may exist per invoice. Issuing returns the linked settlement report to `ready_to_invoice`. Partial credit notes are not supported. Eligibility depends on the B2B invoice processor recorded on the invoice at issuance. An invoice generated through the built-in B2B invoice integration is eligible as soon as it is issued. An invoice generated through a processor that certifies documents with a fiscal authority is eligible only after the original document has been certified — until the document exists at the fiscal authority there is nothing to cancel. Use `fiscalization.status` on the single-invoice read to observe this: `pending` and `failed` mean not yet creditable, `certified` means the precondition is met. Certification is a necessary, not a sufficient, condition — the rare certified document with no recorded `fiscalization.referenceNumber` described under `fiscalization.status` stays ineligible and requires operator intervention. A `425` means the original document has not been certified with the fiscal authority yet, so there is nothing to cancel. Retry once `fiscalization.status` on the single-invoice read reaches `certified`.",
       "tags": [
         "action / partner invoice"
       ],
@@ -3884,7 +3884,10 @@
           "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."
+          "description": "The invoice is permanently ineligible for credit note issuance and the request will not succeed on retry. Returned when the invoice already has a credit note, when the target is itself a credit note, when the B2B invoice processor recorded on the invoice does not support credit note issuance, or when the original document is certified but its fiscal authority number was never recorded on the platform."
+        },
+        "425": {
+          "description": "The original document is not yet certified with the fiscal authority. The invoice becomes creditable once `fiscalization.status` reaches `certified`."
         },
         "429": {
           "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
@@ -3972,6 +3975,57 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/partner-settlement-report/v1.0/{partnerSettlementReport}/set-custom-fields",
+      "method": "POST",
+      "operationId": "partnerSettlementReportSetCustomFields",
+      "summary": "Partner settlement report / 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 applicable live custom field values of a partner settlement report without changing the historical report, its generated documents, party and settings snapshots, or derived partner invoices. This action requires permission to view the partner settlement report and the `PartnerSettlementReports.update-custom-fields` permission. The `customFields` object accepts Boolean, Text, Long text, Email, URL, Number, Date, Date-time and JSON values according to each administrator-defined field. It may be empty. Omitted identifiers remain unchanged, while an explicit `null` clears the corresponding value. Every submitted identifier is validated against the report's current partner owner, the current custom field configuration and the acting administrator's access. Unknown, inapplicable or currently disabled identifiers return a `422` error keyed as `customFields.<identifier>`, and no submitted values are changed. This write action does not accept query parameters or includes. The response is the current default read representation after applying the values; `customFields` remains live metadata and is not a point-in-time representation of the historical settlement report.",
+      "tags": [
+        "action / partner settlement report"
+      ],
+      "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 partner settlement report's default current read representation 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"
+        },
+        "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}/update-external-id",
       "method": "POST",
@@ -4023,6 +4077,108 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/partner/v1.0/{partner}/set-custom-fields",
+      "method": "POST",
+      "operationId": "partnerSetCustomFieldsV1_0",
+      "summary": "Partner / 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 applicable custom field values of a partner without changing any other partner properties. This action requires permission to view the partner and the `Partners.update-custom-fields` permission. Send a JSON object containing only the required `customFields` property. Query parameters and additional body properties are rejected. The `customFields` object may be empty. Omitted identifiers remain unchanged, while an explicit `null` clears the corresponding value. Every submitted identifier is validated against the partner, the current custom field configuration and the acting administrator's access. Unknown, inapplicable or currently disabled identifiers return a `422` error keyed as `customFields.<identifier>`, and no submitted values are changed.",
+      "tags": [
+        "action / partner"
+      ],
+      "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 partner's default v2.0 read representation 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"
+        },
+        "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/payment-terminal/v1.0/{paymentTerminal}/set-custom-fields",
+      "method": "POST",
+      "operationId": "paymentTerminalSetCustomFields",
+      "summary": "Payment terminal / 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 applicable custom field values of a payment terminal without changing any other payment terminal properties. This action requires permission to view the payment terminal and the `PaymentTerminals.update-custom-fields` permission. When custom fields are enabled for payment terminals, the `customFields` object may be empty; an empty object succeeds as a no-op without creating a value audit. Omitted identifiers remain unchanged, while an explicit `null` clears the corresponding value. If custom fields are disabled for the tenant or for payment terminals, an empty object returns a `422` error keyed as `customFields`, while a populated object returns errors keyed as `customFields.<identifier>`. Every submitted identifier is validated against the payment terminal, the current custom field configuration and the acting administrator's access. Unknown or inapplicable identifiers also return a `422` error keyed as `customFields.<identifier>`, and no submitted values are changed.",
+      "tags": [
+        "action / payment terminal"
+      ],
+      "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 payment terminal's v1.1 read representation 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"
+        },
+        "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/provisioning-certificate/v1.0/{provisioningCertificate}/issue-emaid",
       "method": "POST",
@@ -4878,6 +5034,57 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/session/v1.0/{session}/set-custom-fields",
+      "method": "POST",
+      "operationId": "sessionSetCustomFields",
+      "summary": "Session / 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 applicable custom field values of a session without changing any other session properties. This action requires permission to view the session and the `Sessions.update-custom-fields` permission. When custom fields are enabled for sessions, the `customFields` object may be empty; an empty object succeeds as a no-op without creating a value audit. Omitted identifiers remain unchanged, while an explicit `null` clears the corresponding value. If custom fields are disabled for the tenant or for sessions, an empty object returns a `422` error keyed as `customFields`, while a populated object returns errors keyed as `customFields.<identifier>`. Every submitted identifier is validated against the session, the current custom field configuration and the acting administrator's access. Unknown or inapplicable identifiers also return a `422` error keyed as `customFields.<identifier>`, and no submitted values are changed.",
+      "tags": [
+        "action / session"
+      ],
+      "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 session's default read representation 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"
+        },
+        "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/subscription-plans/v1.0/{subscriptionPlan}/replace",
       "method": "POST",
@@ -10841,37 +11048,6 @@
                   "example": "local",
                   "nullable": true,
                   "description": "Calibration law data availability override for Hubject/OICP compliance. Set to `local` if the charger has a certified on-site display for signed meter readings. Set to `not_available` for chargers whose hardware is not calibration-law compliant (e.g. cannot produce signed meter values). Set to `null` to use automatic resolution (External when Eichrecht is supported, Not Available otherwise)."
-                },
-                "powerSharing": {
-                  "type": "object",
-                  "properties": {
-                    "enabled": {
-                      "type": "boolean",
-                      "description": "Whether DC cabinet power sharing is enabled for the charge point."
-                    },
-                    "managementMode": {
-                      "type": "string",
-                      "enum": [
-                        "static",
-                        "dynamic"
-                      ],
-                      "description": "Controls how the charge point allocates cabinet power across its DC outputs. `static` uses power modules dedicated to individual EVSEs; modules are not dynamically shared between EVSEs. `dynamic` shares power modules across EVSEs and allocates cabinet power in discrete steps defined by `moduleSizeKw`."
-                    },
-                    "totalCabinetPowerKw": {
-                      "type": "integer",
-                      "minimum": 1,
-                      "description": "Total power available from the DC cabinet, in kilowatts."
-                    },
-                    "moduleSizeKw": {
-                      "type": "integer",
-                      "minimum": 1,
-                      "description": "Power of one DC cabinet module, in kilowatts."
-                    }
-                  },
-                  "required": [
-                    "enabled"
-                  ],
-                  "description": "DC cabinet power-sharing configuration. When `enabled` is `true`, `totalCabinetPowerKw` and `managementMode` are required. When `managementMode` is `dynamic`, `moduleSizeKw` is required, must not exceed `totalCabinetPowerKw`, and must divide `totalCabinetPowerKw` evenly."
                 }
               },
               "required": [
@@ -11041,37 +11217,6 @@
                   "nullable": true,
                   "description": "Calibration law data availability override for Hubject/OICP compliance. Set to `local` if the charger has a certified on-site display for signed meter readings. Set to `not_available` for chargers whose hardware is not calibration-law compliant (e.g. cannot produce signed meter values). Set to `null` to use automatic resolution (External when Eichrecht is supported, Not Available otherwise)."
                 },
-                "powerSharing": {
-                  "type": "object",
-                  "properties": {
-                    "enabled": {
-                      "type": "boolean",
-                      "description": "Whether DC cabinet power sharing is enabled for the charge point."
-                    },
-                    "managementMode": {
-                      "type": "string",
-                      "enum": [
-                        "static",
-                        "dynamic"
-                      ],
-                      "nullable": true,
-                      "description": "Controls how the charge point allocates cabinet power across its DC outputs. `static` uses power modules dedicated to individual EVSEs; modules are not dynamically shared between EVSEs. `dynamic` shares power modules across EVSEs and allocates cabinet power in discrete steps defined by `moduleSizeKw`."
-                    },
-                    "totalCabinetPowerKw": {
-                      "type": "integer",
-                      "minimum": 1,
-                      "nullable": true,
-                      "description": "Total power available from the DC cabinet, in kilowatts. Set to `null` to clear the configured value."
-                    },
-                    "moduleSizeKw": {
-                      "type": "integer",
-                      "minimum": 1,
-                      "nullable": true,
-                      "description": "Power of one DC cabinet module, in kilowatts. Set to `null` to clear the configured value."
-                    }
-                  },
-                  "description": "Updates the DC cabinet power-sharing configuration. Omitted properties retain their current values and explicit `null` clears a nullable property. The resulting configuration must provide `totalCabinetPowerKw` and `managementMode` when enabled. When `managementMode` is `dynamic`, `moduleSizeKw` is required, must not exceed `totalCabinetPowerKw`, and must divide `totalCabinetPowerKw` evenly. Updating this configuration for a charge point with active sessions triggers an immediate dynamic load management rebalance."
-                },
                 "subscription": {
                   "type": "object",
                   "properties": {
@@ -14131,6 +14276,37 @@
                       ],
                       "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`"
+                    },
+                    "powerSharing": {
+                      "type": "object",
+                      "properties": {
+                        "enabled": {
+                          "type": "boolean",
+                          "description": "Whether DC cabinet power sharing is enabled for the charge point."
+                        },
+                        "managementMode": {
+                          "type": "string",
+                          "enum": [
+                            "static",
+                            "dynamic"
+                          ],
+                          "nullable": true,
+                          "description": "Controls how the charge point allocates cabinet power across its DC outputs. `static` uses power modules dedicated to individual EVSEs; modules are not dynamically shared between EVSEs. `dynamic` shares power modules across EVSEs and allocates cabinet power in discrete steps defined by `moduleSizeKw`."
+                        },
+                        "totalCabinetPowerKw": {
+                          "type": "integer",
+                          "minimum": 1,
+                          "nullable": true,
+                          "description": "Total power available from the DC cabinet, in kilowatts. Set to `null` to clear the configured value."
+                        },
+                        "moduleSizeKw": {
+                          "type": "integer",
+                          "minimum": 1,
+                          "nullable": true,
+                          "description": "Power of one DC cabinet module, in kilowatts. Set to `null` to clear the configured value."
+                        }
+                      },
+                      "description": "Updates the DC cabinet power-sharing configuration. Omitted properties retain their current values and explicit `null` clears a nullable property. The resulting configuration must provide `totalCabinetPowerKw` and `managementMode` when enabled. When `managementMode` is `dynamic`, `moduleSizeKw` is required, must not exceed `totalCabinetPowerKw`, and must divide `totalCabinetPowerKw` evenly. Updating this configuration for a charge point with active sessions triggers an immediate dynamic load management rebalance."
                     }
                   },
                   "required": [
@@ -14231,6 +14407,37 @@
                       ],
                       "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`"
+                    },
+                    "powerSharing": {
+                      "type": "object",
+                      "properties": {
+                        "enabled": {
+                          "type": "boolean",
+                          "description": "Whether DC cabinet power sharing is enabled for the charge point."
+                        },
+                        "managementMode": {
+                          "type": "string",
+                          "enum": [
+                            "static",
+                            "dynamic"
+                          ],
+                          "nullable": true,
+                          "description": "Controls how the charge point allocates cabinet power across its DC outputs. `static` uses power modules dedicated to individual EVSEs; modules are not dynamically shared between EVSEs. `dynamic` shares power modules across EVSEs and allocates cabinet power in discrete steps defined by `moduleSizeKw`."
+                        },
+                        "totalCabinetPowerKw": {
+                          "type": "integer",
+                          "minimum": 1,
+                          "nullable": true,
+                          "description": "Total power available from the DC cabinet, in kilowatts. Set to `null` to clear the configured value."
+                        },
+                        "moduleSizeKw": {
+                          "type": "integer",
+                          "minimum": 1,
+                          "nullable": true,
+                          "description": "Power of one DC cabinet module, in kilowatts. Set to `null` to clear the configured value."
+                        }
+                      },
+                      "description": "Updates the DC cabinet power-sharing configuration. Omitted properties retain their current values and explicit `null` clears a nullable property. The resulting configuration must provide `totalCabinetPowerKw` and `managementMode` when enabled. When `managementMode` is `dynamic`, `moduleSizeKw` is required, must not exceed `totalCabinetPowerKw`, and must divide `totalCabinetPowerKw` evenly. Updating this configuration for a charge point with active sessions triggers an immediate dynamic load management rebalance."
                     }
                   },
                   "required": [
@@ -14335,6 +14542,37 @@
                       ],
                       "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`"
+                    },
+                    "powerSharing": {
+                      "type": "object",
+                      "properties": {
+                        "enabled": {
+                          "type": "boolean",
+                          "description": "Whether DC cabinet power sharing is enabled for the charge point."
+                        },
+                        "managementMode": {
+                          "type": "string",
+                          "enum": [
+                            "static",
+                            "dynamic"
+                          ],
+                          "nullable": true,
+                          "description": "Controls how the charge point allocates cabinet power across its DC outputs. `static` uses power modules dedicated to individual EVSEs; modules are not dynamically shared between EVSEs. `dynamic` shares power modules across EVSEs and allocates cabinet power in discrete steps defined by `moduleSizeKw`."
+                        },
+                        "totalCabinetPowerKw": {
+                          "type": "integer",
+                          "minimum": 1,
+                          "nullable": true,
+                          "description": "Total power available from the DC cabinet, in kilowatts. Set to `null` to clear the configured value."
+                        },
+                        "moduleSizeKw": {
+                          "type": "integer",
+                          "minimum": 1,
+                          "nullable": true,
+                          "description": "Power of one DC cabinet module, in kilowatts. Set to `null` to clear the configured value."
+                        }
+                      },
+                      "description": "Updates the DC cabinet power-sharing configuration. Omitted properties retain their current values and explicit `null` clears a nullable property. The resulting configuration must provide `totalCabinetPowerKw` and `managementMode` when enabled. When `managementMode` is `dynamic`, `moduleSizeKw` is required, must not exceed `totalCabinetPowerKw`, and must divide `totalCabinetPowerKw` evenly. Updating this configuration for a charge point with active sessions triggers an immediate dynamic load management rebalance."
                     }
                   },
                   "required": [
@@ -14360,6 +14598,37 @@
                     "preconditioningTime": {
                       "type": "integer",
                       "description": "The time in minutes before departure when the charging will be performed with full power."
+                    },
+                    "powerSharing": {
+                      "type": "object",
+                      "properties": {
+                        "enabled": {
+                          "type": "boolean",
+                          "description": "Whether DC cabinet power sharing is enabled for the charge point."
+                        },
+                        "managementMode": {
+                          "type": "string",
+                          "enum": [
+                            "static",
+                            "dynamic"
+                          ],
+                          "nullable": true,
+                          "description": "Controls how the charge point allocates cabinet power across its DC outputs. `static` uses power modules dedicated to individual EVSEs; modules are not dynamically shared between EVSEs. `dynamic` shares power modules across EVSEs and allocates cabinet power in discrete steps defined by `moduleSizeKw`."
+                        },
+                        "totalCabinetPowerKw": {
+                          "type": "integer",
+                          "minimum": 1,
+                          "nullable": true,
+                          "description": "Total power available from the DC cabinet, in kilowatts. Set to `null` to clear the configured value."
+                        },
+                        "moduleSizeKw": {
+                          "type": "integer",
+                          "minimum": 1,
+                          "nullable": true,
+                          "description": "Power of one DC cabinet module, in kilowatts. Set to `null` to clear the configured value."
+                        }
+                      },
+                      "description": "Updates the DC cabinet power-sharing configuration. Omitted properties retain their current values and explicit `null` clears a nullable property. The resulting configuration must provide `totalCabinetPowerKw` and `managementMode` when enabled. When `managementMode` is `dynamic`, `moduleSizeKw` is required, must not exceed `totalCabinetPowerKw`, and must divide `totalCabinetPowerKw` evenly. Updating this configuration for a charge point with active sessions triggers an immediate dynamic load management rebalance."
                     }
                   },
                   "required": [
@@ -38069,6 +38338,7 @@
                     "ga-IE",
                     "bs",
                     "ja",
+                    "ko",
                     "cs",
                     "lv",
                     "et",
@@ -38826,6 +39096,11 @@
                   "type": "string",
                   "format": "date"
                 },
+                "customFields": {
+                  "type": "string",
+                  "example": "filter[customFields.invoiceReference]=INV-42",
+                  "description": "Filter a custom-field host resource by custom fields defined for that resource. Add one literal `customFields.<identifier>` key to the existing `filter` object for each criterion. The identifier suffix is administrator-defined and is never enumerated in this schema or generated per tenant. Use a scalar for boolean, text, email, and URL fields. Boolean accepts booleans and integer `1` or `0`, as well as the strings `\"true\"`, `\"false\"`, `\"1\"`, and `\"0\"`. Text, email, and URL accept strings and use contains matching that is case- and accent-insensitive; backslashes, `%`, and `_` are treated literally rather than as pattern syntax. Use `from`, `to`, or both below the dotted key for number, date, and date-time fields. Both bounds are inclusive. Number bounds are decimal strings from `-99999999999999.999999` through `99999999999999.999999` with at most six decimal places; comparisons preserve submitted and stored decimal precision without rounding. Date bounds use `YYYY-MM-DD` and compare calendar dates without time-zone conversion. Date-time bounds use ISO 8601; offsets are normalized to UTC, and an omitted offset is interpreted as UTC. Multiple identifiers combine with AND. Empty scalar criteria and ranges whose bounds are empty are ignored. An identifier resolves only to its current active definition, so values belonging to a deleted definition never match if its identifier is reused. Operator-scoped filters match only host records whose current operator owner is assigned to the field; retained inapplicable values are excluded before pagination. Unknown, inaccessible, tenant-disabled, resource-disabled, deleted, and otherwise unavailable identifiers all return the same non-disclosing `404` response. An active accessible custom field whose filtering is disabled returns `422` with `Custom field \"{identifier}\" is not filterable for resource \"{resource}\".` Malformed objects or values, a criterion shape that is invalid for the field type, and a range whose `from` bound is greater than its `to` bound return `422`. Custom-field filters apply only to resource listings. They do not participate in search and do not depend on an `include` parameter; any unrelated includes are defined by the host resource. Examples: `filter[customFields.invoiceReference]=INV-42` and `filter[customFields.capacity][from]=10&filter[customFields.capacity][to]=20`. URL-encode the query keys and values when sending the request."
+                },
                 "externalId": {
                   "type": "string"
                 }
@@ -38855,6 +39130,9 @@
         "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"
         },
@@ -40796,6 +41074,9 @@
         "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"
         },
@@ -41565,6 +41846,11 @@
                       "default": false,
                       "description": "Allows the Partner to control configurations on their charge points."
                     },
+                    "allowToLogExemptPeriods": {
+                      "type": "boolean",
+                      "default": false,
+                      "description": "Allows Partner admins with the Maintain permission from the DowntimePeriods permission set to log exempt periods."
+                    },
                     "settlementReportBreakdown": {
                       "type": "string",
                       "enum": [
@@ -42621,6 +42907,11 @@
                           "default": false,
                           "description": "Allows the Partner to control configurations on their charge points."
                         },
+                        "allowToLogExemptPeriods": {
+                          "type": "boolean",
+                          "default": false,
+                          "description": "Allows Partner admins with the Maintain permission from the DowntimePeriods permission set to log exempt periods."
+                        },
                         "settlementReportBreakdown": {
                           "type": "string",
                           "enum": [
@@ -45761,7 +46052,13 @@
                   "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`"
                 },
                 "serialNumber": {
-                  "type": "string"
+                  "type": "string",
+                  "description": "Filter payment terminals by serial number or station."
+                },
+                "customFields": {
+                  "type": "object",
+                  "additionalProperties": true,
+                  "description": "Map of administrator-defined custom field identifiers to filter values. Send each entry as `filter[customFields.<identifier>]`."
                 }
               }
             }
@@ -45778,6 +46075,12 @@
         "403": {
           "description": "You do not have permission to perform the action"
         },
+        "404": {
+          "description": "The requested custom field filter identifier is unavailable"
+        },
+        "422": {
+          "description": "The request contains invalid criteria, including malformed or non-filterable custom field filters"
+        },
         "429": {
           "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
         }
@@ -45823,6 +46126,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -45931,6 +46235,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -46185,6 +46490,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -46241,6 +46547,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -46303,6 +46610,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -46363,6 +46671,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -46418,6 +46727,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -46501,6 +46811,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -46556,6 +46867,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -46648,6 +46960,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -46830,6 +47143,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -47025,6 +47339,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -47312,6 +47627,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -47394,6 +47710,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -47559,6 +47876,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -47604,6 +47922,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -47656,6 +47975,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -47705,6 +48025,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -47750,6 +48071,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -47820,6 +48142,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -47865,6 +48188,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -47896,6 +48220,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -48011,6 +48336,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -48118,6 +48444,7 @@
                         "Windcave",
                         "Web portal",
                         "AdyenCastles",
+                        "Adyen Castles",
                         "Printec Castles",
                         "Cardlink Castles"
                       ]
@@ -51959,7 +52286,7 @@
                 "customFields": {
                   "type": "string",
                   "example": "filter[customFields.invoiceReference]=INV-42",
-                  "description": "Filter sessions by custom fields defined for the session resource. Add one literal `customFields.<identifier>` key to the existing `filter` object for each criterion. The identifier suffix is administrator-defined and is not enumerated in this schema. Use a scalar for boolean, text, email, and URL fields. Boolean accepts booleans and integer `1` or `0`, as well as the strings `\"true\"`, `\"false\"`, `\"1\"`, and `\"0\"`. Text, email, and URL accept strings and use contains matching that is case- and accent-insensitive; backslashes, `%`, and `_` are treated literally rather than as pattern syntax. Use `from`, `to`, or both below the dotted key for number, date, and date-time fields. Both bounds are inclusive. Number bounds are decimal strings from `-99999999999999.999999` through `99999999999999.999999` with at most six decimal places; comparisons preserve submitted and stored decimal precision without rounding. Date bounds use `YYYY-MM-DD` and compare calendar dates without time-zone conversion. Date-time bounds use ISO 8601; offsets are normalized to UTC, and an omitted offset is interpreted as UTC. Multiple identifiers combine with AND. Empty scalar criteria and ranges whose bounds are empty are ignored. An identifier resolves only to its current active definition, so values belonging to a deleted definition never match if its identifier is reused. Unknown, inaccessible, tenant-disabled, resource-disabled, deleted, and otherwise unavailable identifiers all return the same non-disclosing `404` response. An active accessible custom field whose filtering is disabled returns `422` with `Custom field \"{identifier}\" is not filterable for resource \"{resource}\".` Malformed objects or values, a criterion shape that is invalid for the field type, and a range whose `from` bound is greater than its `to` bound return `422`. Examples: `filter[customFields.invoiceReference]=INV-42` and `filter[customFields.capacity][from]=10&filter[customFields.capacity][to]=20`. URL-encode the query keys and values when sending the request."
+                  "description": "Filter a custom-field host resource by custom fields defined for that resource. Add one literal `customFields.<identifier>` key to the existing `filter` object for each criterion. The identifier suffix is administrator-defined and is never enumerated in this schema or generated per tenant. Use a scalar for boolean, text, email, and URL fields. Boolean accepts booleans and integer `1` or `0`, as well as the strings `\"true\"`, `\"false\"`, `\"1\"`, and `\"0\"`. Text, email, and URL accept strings and use contains matching that is case- and accent-insensitive; backslashes, `%`, and `_` are treated literally rather than as pattern syntax. Use `from`, `to`, or both below the dotted key for number, date, and date-time fields. Both bounds are inclusive. Number bounds are decimal strings from `-99999999999999.999999` through `99999999999999.999999` with at most six decimal places; comparisons preserve submitted and stored decimal precision without rounding. Date bounds use `YYYY-MM-DD` and compare calendar dates without time-zone conversion. Date-time bounds use ISO 8601; offsets are normalized to UTC, and an omitted offset is interpreted as UTC. Multiple identifiers combine with AND. Empty scalar criteria and ranges whose bounds are empty are ignored. An identifier resolves only to its current active definition, so values belonging to a deleted definition never match if its identifier is reused. Operator-scoped filters match only host records whose current operator owner is assigned to the field; retained inapplicable values are excluded before pagination. Unknown, inaccessible, tenant-disabled, resource-disabled, deleted, and otherwise unavailable identifiers all return the same non-disclosing `404` response. An active accessible custom field whose filtering is disabled returns `422` with `Custom field \"{identifier}\" is not filterable for resource \"{resource}\".` Malformed objects or values, a criterion shape that is invalid for the field type, and a range whose `from` bound is greater than its `to` bound return `422`. Custom-field filters apply only to resource listings. They do not participate in search and do not depend on an `include` parameter; any unrelated includes are defined by the host resource. Examples: `filter[customFields.invoiceReference]=INV-42` and `filter[customFields.capacity][from]=10&filter[customFields.capacity][to]=20`. URL-encode the query keys and values when sending the request."
                 }
               }
             }
@@ -52070,7 +52397,7 @@
             "default": false
           },
           "include": {
-            "description": "Include additional information in the response. The following options are available:<br> - `externalAppData`: Include external application data in the response<br> - `chargingProfile`: Include the TX charging profile applied to the session in the response<br> - `vehicle`: Include the nested `vehicle` object describing the vehicle associated with the session",
+            "description": "Include additional information in the response. The following options are available:<br> - `externalAppData`: Include external application data in the response<br> - `chargingProfile`: Include the TX charging profile applied to the session in the response<br> - `vehicle`: Include the nested `vehicle` object describing the vehicle associated with the session<br> - `timelineSnapshot`: Include the pre-computed timeline snapshot for a finished session when available",
             "schema": {
               "type": "array",
               "items": {
@@ -52078,7 +52405,8 @@
                 "enum": [
                   "externalAppData",
                   "chargingProfile",
-                  "vehicle"
+                  "vehicle",
+                  "timelineSnapshot"
                 ]
               }
             }
@@ -52106,66 +52434,6 @@
         }
       }
     },
-    {
-      "path": "/public-api/resources/sessions/v1.0/{session}",
-      "method": "PATCH",
-      "operationId": "sessionUpdate",
-      "summary": "Session / 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 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. Update the applicable custom field values of a session without changing any other session properties.",
-      "tags": [
-        "resource / sessions"
-      ],
-      "parameters": {
-        "path": {
-          "session": {
-            "description": "The session ID to fetch",
-            "type": "string",
-            "required": true
-          }
-        }
-      },
-      "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. Omitted identifiers remain unchanged, and a `null` value clears the corresponding custom field. 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": {
-        "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/sessions/v1.0/{session}/consumption-stats",
       "method": "GET",
@@ -52243,7 +52511,7 @@
       "method": "GET",
       "operationId": "sessionTimelineSnapshotRead",
       "summary": "Sessions / Timeline Snapshot / Read",
-      "description": "Returns the meter value time-series and lifecycle events for a finished charging session. **Availability.** Snapshots are generated when a session completes. Active sessions return 404. Finished sessions without snapshots, including sessions that finished before snapshot generation was available, also return 404. There is no historical backfill. **For active sessions**, use `GET /logs/communication/v1.0?filter[sessionId]={id}&filter[command]=MeterValues` to read real-time OCPP meter values from communication logs (6-month retention).",
+      "description": "Returns the meter value time-series and lifecycle events for a finished charging session. **Availability.** Snapshots are generated when a session completes. Active sessions return 404. Finished sessions without snapshots, including sessions that finished before snapshot generation was available, also return 404. There is no historical backfill. Confirmed transaction boundary events are included only in snapshots generated after those event types became available; existing snapshots are not modified. A boundary event is omitted when its timestamp or precise meter reading is unavailable. **For active sessions**, use `GET /logs/communication/v1.0?filter[sessionId]={id}&filter[command]=MeterValues` to read real-time OCPP meter values from communication logs (6-month retention).",
       "tags": [
         "resource / sessions"
       ],
@@ -62835,10 +63103,11 @@
                       "bank_transfer_pending",
                       "bank_transfer_processing",
                       "payment_terminal_authorization",
+                      "awaiting_reconciliation",
                       "other"
                     ],
                     "example": "3ds_authentication",
-                    "description": "Reason a transaction is currently pending. Available only while `status` is `pending`; omitted once the transaction reaches a terminal status. The property may also be absent on a pending transaction when no specific reason has been recorded — for example legacy transactions created before the enum rolled out to all PSPs, or transactions handled by a payment service provider that does not yet report a pending reason. - **3ds_authentication**: Transaction requires 3D Secure verification from the user - **psp_processing**: Payment processor is processing the transaction - **bank_transfer_pending**: User needs to complete the bank transfer redirect - **bank_transfer_processing**: Bank transfer initiated, awaiting confirmation - **payment_terminal_authorization**: Waiting for payment terminal authorization - **other**: Pending but the reason does not fit any of the defined categories"
+                    "description": "Reason a transaction is currently pending. Available only while `status` is `pending`; omitted once the transaction reaches a terminal status. The property may also be absent on a pending transaction when no specific reason has been recorded — for example legacy transactions created before the enum rolled out to all PSPs, or transactions handled by a payment service provider that does not yet report a pending reason. - **3ds_authentication**: Transaction requires 3D Secure verification from the user - **psp_processing**: Payment processor is processing the transaction - **bank_transfer_pending**: User needs to complete the bank transfer redirect - **bank_transfer_processing**: Bank transfer initiated, awaiting confirmation - **payment_terminal_authorization**: Waiting for payment terminal authorization - **awaiting_reconciliation**: The payment is handled by a payment terminal on the charge point, and the transaction is waiting to be reconciled with the amount that terminal settles. The amount currently on the transaction is provisional until reconciliation completes. - **other**: Pending but the reason does not fit any of the defined categories"
                   },
                   "description": "Only list transactions with the specified pending reason(s). When this filter is applied, results are implicitly limited to transactions whose status is `pending`."
                 },
@@ -68830,6 +69099,7 @@
                     "ga-IE",
                     "bs",
                     "ja",
+                    "ko",
                     "cs",
                     "lv",
                     "et",
@@ -69750,6 +70020,7 @@
                     "ga-IE",
                     "bs",
                     "ja",
+                    "ko",
                     "cs",
                     "lv",
                     "et",
@@ -71928,7 +72199,7 @@
   ],
   "info": {
     "title": "Public API",
-    "version": "3.247.2",
+    "version": "3.248.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": [
@@ -71942,18 +72213,18 @@
       }
     }
   ],
-  "buildTimestamp": "2026-09-11T12:09:11.484Z",
+  "buildTimestamp": "2026-09-14T13:02:49.113Z",
   "stats": {
-    "totalEndpoints": 640,
-    "originalSize": 5828593,
-    "optimizedSize": 1631472,
-    "reductionPercent": 72.01,
-    "buildDuration": 1625,
+    "totalEndpoints": 643,
+    "originalSize": 5956908,
+    "optimizedSize": 1651756,
+    "reductionPercent": 72.27,
+    "buildDuration": 1576,
     "responseSchemas": {
-      "total": 640,
-      "withSchemas": 640,
-      "totalSchemaSize": 3317461,
-      "averageSchemaSize": 5184
+      "total": 643,
+      "withSchemas": 643,
+      "totalSchemaSize": 3413991,
+      "averageSchemaSize": 5309
     }
   }
 }