@ampeco/public-api-mcp 3.254.3 → 3.255.1

package/dist/generated/build-stats.json

@@ -1,13 +1,13 @@
 {
   "totalEndpoints": 657,
-  "originalSize": 6140006,
-  "optimizedSize": 1714637,
+  "originalSize": 6159653,
+  "optimizedSize": 1720553,
   "reductionPercent": 72.07,
-  "buildDuration": 1600,
+  "buildDuration": 1481,
   "responseSchemas": {
     "total": 657,
     "withSchemas": 657,
-    "totalSchemaSize": 3519465,
-    "averageSchemaSize": 5357
+    "totalSchemaSize": 3531263,
+    "averageSchemaSize": 5375
   }
 }

package/dist/generated/endpoints.json

@@ -9077,14 +9077,17 @@
                 "status": {
                   "type": "string",
                   "enum": [
+                    "pending",
                     "accepted",
+                    "rejected",
                     "reserved",
                     "completed",
                     "cancelled",
                     "no-show",
                     "failed"
                   ],
-                  "description": "Filter by booking status"
+                  "example": "accepted",
+                  "description": "Status of booking: - **pending**: Booking has been requested and is awaiting an asynchronous decision - **accepted**: Booking has been approved and confirmed - **rejected**: Booking request has been declined - **reserved**: EVSE has been reserved via OCPP ReserveNow command - **completed**: User has started a charging session and fulfilled the booking - **cancelled**: Booking has been cancelled by user or system - **no-show**: User failed to start session within the no-show timeout period - **failed**: The booking could not be established - either the EVSE could not be reserved after multiple attempts, or the request could not be decided"
                 },
                 "userId": {
                   "type": "integer",
@@ -11177,21 +11180,23 @@
                       "type": "string",
                       "enum": [
                         "ocpp 1.5",
+                        "ocpp 1.5 json",
                         "ocpp 1.6",
                         "ocpp 1.6 soap",
                         "ocpp 2.0.1"
-                      ]
+                      ],
+                      "description": "Charge point OCPP protocol and transport: - **ocpp 1.5**: OCPP 1.5 over SOAP - **ocpp 1.5 json**: OCPP 1.5 over JSON - **ocpp 1.6**: OCPP 1.6 over JSON - **ocpp 1.6 soap**: OCPP 1.6 over SOAP - **ocpp 2.0.1**: OCPP 2.0.1 over JSON"
                     },
                     "password": {
                       "type": "string"
                     },
                     "ip": {
                       "type": "string",
-                      "description": "Required for ocpp 1.5 (SOAP)"
+                      "description": "Required for communication over SOAP (OCPP 1.5 and OCPP 1.6)."
                     },
                     "port": {
                       "type": "integer",
-                      "description": "Required for ocpp 1.5 (SOAP)"
+                      "description": "Required for communication over SOAP (OCPP 1.5 and OCPP 1.6)."
                     }
                   },
                   "description": "Required and non-empty for charge points communicating directly over OCPP, which is the default communication mode. The requirement applies when `communicationMode` is `direct_ocpp`, or when `communicationMode` is omitted and `managedByOperator` is omitted or `true`; it does not apply to `none`, `via_ocpp_connected_charge_point`, or `managedByOperator: false` charge points."
@@ -11639,11 +11644,13 @@
                       "type": "string",
                       "enum": [
                         "ocpp 1.5",
+                        "ocpp 1.5 json",
                         "ocpp 1.6",
                         "ocpp 1.6 soap",
                         "ocpp 2.0.1"
                       ],
-                      "nullable": true
+                      "nullable": true,
+                      "description": "Charge point OCPP protocol and transport: - **ocpp 1.5**: OCPP 1.5 over SOAP - **ocpp 1.5 json**: OCPP 1.5 over JSON - **ocpp 1.6**: OCPP 1.6 over JSON - **ocpp 1.6 soap**: OCPP 1.6 over SOAP - **ocpp 2.0.1**: OCPP 2.0.1 over JSON"
                     },
                     "password": {
                       "type": "string",
@@ -11652,12 +11659,12 @@
                     "ip": {
                       "type": "string",
                       "nullable": true,
-                      "description": "Required for ocpp 1.5 (SOAP)"
+                      "description": "Required for communication over SOAP (OCPP 1.5 and OCPP 1.6)."
                     },
                     "port": {
                       "type": "integer",
                       "nullable": true,
-                      "description": "Required for ocpp 1.5 (SOAP)"
+                      "description": "Required for communication over SOAP (OCPP 1.5 and OCPP 1.6)."
                     }
                   }
                 },
@@ -39200,6 +39207,7 @@
                     "en",
                     "be",
                     "bg",
+                    "fa",
                     "bn",
                     "mk",
                     "el",
@@ -39232,6 +39240,7 @@
                     "ro",
                     "lt",
                     "uk",
+                    "ur",
                     "ru",
                     "nl",
                     "ca-ES",
@@ -40008,7 +40017,7 @@
                 "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. Criteria for unknown, inaccessible, disabled, or deleted custom fields, and for fields whose filtering is disabled or whose type does not support filtering, are ignored; the other criteria in the same request still apply. For a filterable field, 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."
+                  "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. Criteria the request cannot use return `400` and name the rejected keys, and no criterion in the request is applied. This covers unknown, inaccessible, disabled, and deleted identifiers, and fields whose filtering is disabled or whose type does not support filtering. For a usable field, 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"
@@ -40033,6 +40042,9 @@
         "200": {
           "description": "Success"
         },
+        "400": {
+          "description": "Bad Request"
+        },
         "401": {
           "description": "Access token is missing or invalid"
         },
@@ -41977,6 +41989,9 @@
         "200": {
           "description": "Success"
         },
+        "400": {
+          "description": "Bad Request"
+        },
         "401": {
           "description": "Access token is missing or invalid"
         },
@@ -46978,6 +46993,9 @@
         "200": {
           "description": "Success"
         },
+        "400": {
+          "description": "Bad Request"
+        },
         "401": {
           "description": "Access token is missing or invalid"
         },
@@ -50199,7 +50217,7 @@
                 "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. Criteria for unknown, inaccessible, disabled, or deleted custom fields, and for fields whose filtering is disabled or whose type does not support filtering, are ignored; the other criteria in the same request still apply. For a filterable field, 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."
+                  "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. Criteria the request cannot use return `400` and name the rejected keys, and no criterion in the request is applied. This covers unknown, inaccessible, disabled, and deleted identifiers, and fields whose filtering is disabled or whose type does not support filtering. For a usable field, 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."
                 }
               }
             }
@@ -50259,7 +50277,7 @@
       "method": "GET",
       "operationId": "reimbursementReportsListing",
       "summary": "Reimbursement reports / 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 all reimbursement reports. A report is a periodic aggregate that groups the reimbursement records sharing a beneficiary, payer and period, and exposes their totals. For the per-session entries behind those totals, use the reimbursement records listing. Custom-field criteria use `filter[customFields.<identifier>]` keys and compose with the ordinary report filters before cursor pagination. Use scalar values for exact or text criteria and `from`, `to`, or both below the dotted key for ranges. Boolean `false` and integer `0` are active criteria; empty or whitespace-only scalars and ranges with no filled bounds are ignored. Criteria for unknown, disabled, deleted, or non-filterable custom fields are also ignored, while the other criteria in the same request still apply. A malformed value for a filterable custom field returns `422`. Examples: `filter[customFields.invoiceReference]=INV-42`, `filter[customFields.capacity][from]=10`, and `filter[customFields.capacity][from]=10&filter[customFields.capacity][to]=20`. Custom fields do not participate in search.",
+      "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 all reimbursement reports. A report is a periodic aggregate that groups the reimbursement records sharing a beneficiary, payer and period, and exposes their totals. For the per-session entries behind those totals, use the reimbursement records listing. Custom-field criteria use `filter[customFields.<identifier>]` keys and compose with the ordinary report filters before cursor pagination. Use scalar values for exact or text criteria and `from`, `to`, or both below the dotted key for ranges. Boolean `false` and integer `0` are active criteria; empty or whitespace-only scalars and ranges with no filled bounds are ignored. Criteria for unknown, inaccessible, disabled, deleted, or non-filterable custom fields return `400` and name the rejected keys. A malformed value for a usable custom field returns `422`. Examples: `filter[customFields.invoiceReference]=INV-42`, `filter[customFields.capacity][from]=10`, and `filter[customFields.capacity][from]=10&filter[customFields.capacity][to]=20`. Custom fields do not participate in search.",
       "tags": [
         "resource / reimbursement reports"
       ],
@@ -53204,7 +53222,7 @@
                 "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. Criteria for unknown, inaccessible, disabled, or deleted custom fields, and for fields whose filtering is disabled or whose type does not support filtering, are ignored; the other criteria in the same request still apply. For a filterable field, 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."
+                  "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. Criteria the request cannot use return `400` and name the rejected keys, and no criterion in the request is applied. This covers unknown, inaccessible, disabled, and deleted identifiers, and fields whose filtering is disabled or whose type does not support filtering. For a usable field, 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."
                 }
               }
             }
@@ -53243,6 +53261,9 @@
         "200": {
           "description": "Success"
         },
+        "400": {
+          "description": "Bad Request"
+        },
         "401": {
           "description": "Access token is missing or invalid"
         },
@@ -58070,6 +58091,17 @@
                       "nullable": true,
                       "description": "Connection Fee Minimum Session Energy (kWh). Optional. Up to 5 digits after the decimal point depending on the currency precision."
                     },
+                    "connectionFeeMaximumSessionDuration": {
+                      "type": "integer",
+                      "nullable": true,
+                      "description": "Connection fee maximum session duration in minutes. Optional. The connection fee is not charged once the session duration exceeds this value. Applicable for duration+energy and duration+energy time of day. Whole minutes, greater than zero, and strictly greater than connectionFeeMinimumSessionDuration when that is configured."
+                    },
+                    "connectionFeeMaximumSessionEnergy": {
+                      "type": "number",
+                      "format": "decimal",
+                      "nullable": true,
+                      "description": "Connection fee maximum session energy in kWh. Optional. The connection fee is not charged once the energy consumed exceeds this value. Applicable for duration+energy and duration+energy time of day. Greater than zero with up to 2 digits after the decimal point, and strictly greater than connectionFeeMinimumSessionEnergy when that is configured."
+                    },
                     "durationFeeGracePeriod": {
                       "type": "integer",
                       "nullable": true,
@@ -59196,6 +59228,17 @@
                       "nullable": true,
                       "description": "Connection Fee Minimum Session Energy (kWh). Optional. Up to 5 digits after the decimal point depending on the currency precision."
                     },
+                    "connectionFeeMaximumSessionDuration": {
+                      "type": "integer",
+                      "nullable": true,
+                      "description": "Connection fee maximum session duration in minutes. Optional. The connection fee is not charged once the session duration exceeds this value. Applicable for duration+energy and duration+energy time of day. Whole minutes, greater than zero, and strictly greater than connectionFeeMinimumSessionDuration when that is configured."
+                    },
+                    "connectionFeeMaximumSessionEnergy": {
+                      "type": "number",
+                      "format": "decimal",
+                      "nullable": true,
+                      "description": "Connection fee maximum session energy in kWh. Optional. The connection fee is not charged once the energy consumed exceeds this value. Applicable for duration+energy and duration+energy time of day. Greater than zero with up to 2 digits after the decimal point, and strictly greater than connectionFeeMinimumSessionEnergy when that is configured."
+                    },
                     "durationFeeGracePeriod": {
                       "type": "integer",
                       "nullable": true,
@@ -60348,6 +60391,17 @@
                       "nullable": true,
                       "description": "Connection Fee Minimum Session Energy (kWh). Optional. Up to 5 digits after the decimal point depending on the currency precision."
                     },
+                    "connectionFeeMaximumSessionDuration": {
+                      "type": "integer",
+                      "nullable": true,
+                      "description": "Connection fee maximum session duration in minutes. Optional. The connection fee is not charged once the session duration exceeds this value. Applicable for duration+energy and duration+energy time of day. Whole minutes, greater than zero, and strictly greater than connectionFeeMinimumSessionDuration when that is configured."
+                    },
+                    "connectionFeeMaximumSessionEnergy": {
+                      "type": "number",
+                      "format": "decimal",
+                      "nullable": true,
+                      "description": "Connection fee maximum session energy in kWh. Optional. The connection fee is not charged once the energy consumed exceeds this value. Applicable for duration+energy and duration+energy time of day. Greater than zero with up to 2 digits after the decimal point, and strictly greater than connectionFeeMinimumSessionEnergy when that is configured."
+                    },
                     "durationFeeGracePeriod": {
                       "type": "integer",
                       "nullable": true,
@@ -61545,6 +61599,17 @@
                       "nullable": true,
                       "description": "Connection Fee Minimum Session Energy (kWh). Optional. Up to 5 digits after the decimal point depending on the currency precision."
                     },
+                    "connectionFeeMaximumSessionDuration": {
+                      "type": "integer",
+                      "nullable": true,
+                      "description": "Connection fee maximum session duration in minutes. Optional. The connection fee is not charged once the session duration exceeds this value. Applicable for duration+energy and duration+energy time of day. Whole minutes, greater than zero, and strictly greater than connectionFeeMinimumSessionDuration when that is configured."
+                    },
+                    "connectionFeeMaximumSessionEnergy": {
+                      "type": "number",
+                      "format": "decimal",
+                      "nullable": true,
+                      "description": "Connection fee maximum session energy in kWh. Optional. The connection fee is not charged once the energy consumed exceeds this value. Applicable for duration+energy and duration+energy time of day. Greater than zero with up to 2 digits after the decimal point, and strictly greater than connectionFeeMinimumSessionEnergy when that is configured."
+                    },
                     "durationFeeGracePeriod": {
                       "type": "integer",
                       "nullable": true,
@@ -62485,6 +62550,17 @@
                       "nullable": true,
                       "description": "Connection Fee Minimum Session Energy (kWh). Optional. Up to 5 digits after the decimal point depending on the currency precision."
                     },
+                    "connectionFeeMaximumSessionDuration": {
+                      "type": "integer",
+                      "nullable": true,
+                      "description": "Connection fee maximum session duration in minutes. Optional. The connection fee is not charged once the session duration exceeds this value. Applicable for duration+energy and duration+energy time of day. Whole minutes, greater than zero, and strictly greater than connectionFeeMinimumSessionDuration when that is configured."
+                    },
+                    "connectionFeeMaximumSessionEnergy": {
+                      "type": "number",
+                      "format": "decimal",
+                      "nullable": true,
+                      "description": "Connection fee maximum session energy in kWh. Optional. The connection fee is not charged once the energy consumed exceeds this value. Applicable for duration+energy and duration+energy time of day. Greater than zero with up to 2 digits after the decimal point, and strictly greater than connectionFeeMinimumSessionEnergy when that is configured."
+                    },
                     "durationFeeGracePeriod": {
                       "type": "integer",
                       "nullable": true,
@@ -73287,7 +73363,7 @@
   ],
   "info": {
     "title": "Public API",
-    "version": "3.254.3",
+    "version": "3.255.1",
     "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": [
@@ -73301,18 +73377,18 @@
       }
     }
   ],
-  "buildTimestamp": "2026-09-29T07:09:50.519Z",
+  "buildTimestamp": "2026-09-29T09:58:23.904Z",
   "stats": {
     "totalEndpoints": 657,
-    "originalSize": 6140006,
-    "optimizedSize": 1714637,
+    "originalSize": 6159653,
+    "optimizedSize": 1720553,
     "reductionPercent": 72.07,
-    "buildDuration": 1600,
+    "buildDuration": 1481,
     "responseSchemas": {
       "total": 657,
       "withSchemas": 657,
-      "totalSchemaSize": 3519465,
-      "averageSchemaSize": 5357
+      "totalSchemaSize": 3531263,
+      "averageSchemaSize": 5375
     }
   }
 }