@ampeco/public-api-mcp 3.253.1 → 3.254.1

package/dist/generated/endpoints.json

@@ -3987,7 +3987,7 @@
       "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.",
+      "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. Send a JSON object containing the required `customFields` object. Omitted identifiers remain unchanged, while `null` clears the corresponding value. When custom fields are enabled for partner settlement reports, an empty object succeeds as a no-op. Invalid or unavailable identifiers, invalid values, and disabled custom fields return `422` validation errors, and no submitted values are changed. A `404` response means the partner settlement report was not found. 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"
       ],
@@ -4089,7 +4089,7 @@
       "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.",
+      "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 the required `customFields` object. Omitted identifiers remain unchanged, while `null` clears the corresponding value. When custom fields are enabled for partners, an empty object succeeds as a no-op. Invalid or unavailable identifiers, invalid values, and disabled custom fields return `422` validation errors, and no submitted values are changed. A `404` response means the partner was not found.",
       "tags": [
         "action / partner"
       ],
@@ -4140,7 +4140,7 @@
       "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.",
+      "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. Send a JSON object containing the required `customFields` object. Omitted identifiers remain unchanged, while `null` clears the corresponding value. When custom fields are enabled for payment terminals, an empty object succeeds as a no-op. Invalid or unavailable identifiers, invalid values, and disabled custom fields return `422` validation errors, and no submitted values are changed. A `404` response means the payment terminal was not found.",
       "tags": [
         "action / payment terminal"
       ],
@@ -4274,8 +4274,8 @@
         }
       },
       "responses": {
-        "201": {
-          "description": "Credit record created"
+        "202": {
+          "description": "Credit record issued"
         },
         "401": {
           "description": "Access token is missing or invalid"
@@ -4297,6 +4297,57 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/reimbursement-record/v1.0/{reimbursementRecord}/set-custom-fields",
+      "method": "POST",
+      "operationId": "reimbursementRecordSetCustomFieldsV1_0",
+      "summary": "Reimbursement record / 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 reimbursement record without changing its immutable financial, policy, tag, calculation, or timestamp data. This action requires permission to view the reimbursement record and the `ReimbursementRecords.update-custom-fields` permission. Send a JSON object containing the required `customFields` object. Omitted identifiers remain unchanged, while `null` clears the corresponding value. When custom fields are enabled for reimbursement records, an empty object succeeds as a no-op. Invalid or unavailable identifiers, invalid values, and disabled custom fields return `422` validation errors, and no submitted values are changed. A `404` response means the reimbursement record was not found.",
+      "tags": [
+        "action / reimbursement record"
+      ],
+      "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 reimbursement record's 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/reimbursement-report/v1.0/{reimbursementReport}/regenerate",
       "method": "POST",
@@ -4324,6 +4375,57 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/reimbursement-report/v1.0/{reimbursementReport}/set-custom-fields",
+      "method": "POST",
+      "operationId": "reimbursementReportSetCustomFieldsV1_0",
+      "summary": "Reimbursement 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 reimbursement report without changing the report, its constituent reimbursement records, timestamps or generated output. This action requires permission to view the reimbursement report and the `ReimbursementReports.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 operator 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, including the report's prepared monetary aggregates; `customFields` remains live metadata and is not a point-in-time snapshot.",
+      "tags": [
+        "action / reimbursement 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 reimbursement 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/reservation/v1.0/{reservation}/cancel",
       "method": "POST",
@@ -4946,7 +5048,7 @@
       "method": "POST",
       "operationId": "sessionChangeTariff",
       "summary": "Session / Change tariff",
-      "description": "Change the tariff for a session and trigger recalculation of charging periods. This action supports loyalty program integrations where discounts need to be applied mid-session. The tariff change is only available when: - Billing status is NOT \"Completed\" - For running sessions: duration is under 3 hours - For roaming sessions (the platform as eMSP): session must be finished and have a CDR received - No recalculation is already in progress - For local charge point sessions: a StartTransaction message must exist - The selected tariff already has usable concrete pricing",
+      "description": "Change the tariff for a session and trigger recalculation of charging periods. This action supports loyalty program integrations where discounts need to be applied mid-session. The tariff change is only available when: - Billing status is NOT \"Completed\" - For running sessions: duration is under 3 hours - For roaming sessions (the platform as eMSP): session must be finished and have a CDR received - No recalculation is already in progress - For local charge point sessions: a StartTransaction message must exist - The session's billing is not owned by an upstream roaming partner (broker sessions with upstream-sourced CDRs) - The selected tariff already has usable concrete pricing",
       "tags": [
         "action / session"
       ],
@@ -4960,6 +5062,11 @@
                 "tariffId": {
                   "type": "integer",
                   "description": "The ID of the tariff to apply to the session. The tariff must already have usable concrete pricing; unresolved markup or discount tariff definitions cannot be assigned directly and produce a tariffId validation error (422)."
+                },
+                "reason": {
+                  "type": "string",
+                  "maxLength": 1000,
+                  "description": "Optionally, add a reason (e.g., wrong tariff applied at session start, billing dispute)."
                 }
               },
               "required": [
@@ -4983,11 +5090,180 @@
           "description": "The record is not found"
         },
         "409": {
-          "description": "Conflict - The request cannot be completed due to a conflict with the current state of the resource. Possible errors: * Billing is already completed for this session * Session duration exceeds 3 hours (running sessions only) * Roaming session without a CDR * Recalculation already in progress * StartTransaction message missing (local CP sessions)"
+          "description": "Conflict - The request cannot be completed due to a conflict with the current state of the resource. Possible errors: * Billing is already completed for this session * Session duration exceeds 3 hours (running sessions only) * Roaming session without a CDR * Recalculation already in progress * StartTransaction message missing (local CP sessions) * Billing is owned by the upstream roaming partner (broker sessions with upstream-sourced CDRs)"
+        },
+        "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/session/v1.0/{session}/expedite-billing",
+      "method": "POST",
+      "operationId": "sessionExpediteBilling",
+      "summary": "Session / Expedite billing",
+      "description": "Run the billing validation for a finished session that is still awaiting it, instead of waiting for the platform to process it. The action runs as the token owner, who is recorded on the session edit log and on the action audit record. Requires the `Sessions.resume-billing` permission - a token whose admin does not hold it is rejected with 403, and so is a request for a session that belongs to another operator. An unknown session ID is rejected with 404. Preconditions, with the response code each failure produces: * `status` is `finished` and `billingStatus` is `pending` - otherwise 409 * Idle fees are no longer accruing: the connector is disengaged, or the platform settings do not defer billing until the connector is disengaged - otherwise 409 * Billing for the session is not owned by the upstream roaming partner - otherwise 409 * No recalculation is running for the session and the session is not locked for billing processing - otherwise 423 * `reason` is at most 1000 characters - otherwise 422 The validation decides the resulting billing status: | Validation outcome | Resulting billing status | | --- | --- | | Every validation rule passes | `completed` | | A validation rule fails and is configured to suspend billing | `suspended` | | A validation rule fails but is not configured to suspend billing | `completed` | | The session extends an earlier one while the platform settings do not bill extending sessions, or it is a free session on a personal charge point | `completed`, without running the validation rules |",
+      "tags": [
+        "action / session"
+      ],
+      "requestBody": {
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "reason": {
+                  "type": "string",
+                  "maxLength": 1000,
+                  "description": "Reason for expediting billing, recorded on the session edit log."
+                }
+              }
+            }
+          }
+        }
+      },
+      "responses": {
+        "202": {
+          "description": "Action accepted. The billing validation has been run and the billing status updated accordingly."
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "409": {
+          "description": "Conflict - The request cannot be completed due to a conflict with the current state of the session. Possible errors: * The session `status` is not `finished`, or `billingStatus` is not `pending` * Idle fees are still accruing because the connector is still engaged * Billing for this session is owned by the upstream roaming partner"
         },
         "422": {
           "description": "The payload you provided is invalid"
         },
+        "423": {
+          "description": "Locked - The session is temporarily locked because billing is being processed for it, or because a recalculation is already running. Retry later."
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/actions/session/v1.0/{session}/recalculate",
+      "method": "POST",
+      "operationId": "sessionRecalculate",
+      "summary": "Session / Recalculate",
+      "description": "Recalculate a session from its meter values: the existing charging periods are removed and rebuilt, the session metrics are recomputed, the validation rules are re-run and the billing status is updated from the result. The action runs as the token owner, who is recorded on the session edit log and on the action audit record. Requires the `Sessions.resume-billing` permission - a token whose admin does not hold it is rejected with 403, and so is a request for a session that belongs to another operator. An unknown session ID is rejected with 404. Preconditions, with the response code each failure produces: * `billingStatus` is not `completed` - otherwise 409 * Billing for the session is not owned by the upstream roaming partner - otherwise 409 * `status` is `finished`, or `pending` or `active` for a session that is already underway at the charge point - otherwise 409. Not every `pending` or `active` session qualifies: `pending` also covers a session that has not been sent to the charge point yet, and `active` also covers a session that has stopped and is waiting for the cable to be unlocked - both are rejected. * The StartTransaction message is still present in the session's communication logs - otherwise 409 * No recalculation is running for the session and the session is not locked for billing processing - otherwise 423 * `reason` is at most 1000 characters - otherwise 422 **202 means accepted, not recalculated.** The recalculation is queued and runs asynchronously, so a successful response only states that the preconditions held and the work was scheduled; the recalculation itself can still fail afterwards, in which case the session is restored to its previous state. Two outcome channels report the final result: subscribe to the `SessionUpdateNotification` callback, or poll the session resource. `billingStatus` passes through `pending` while the session is being recalculated before settling on its final value; for a session that is still underway it stays `pending` and the validation rules are not run until the session stops. Three risks are inherent to the recalculation and are not prevented by the platform: * The recalculation replays the session's communication logs. Those logs are rotated, so a session old enough to have lost them can no longer be recalculated even though every other precondition holds. * The recalculation prices the session against the tariff captured when the session started, not the tariff in effect now. Editing or deleting the tariff after the session ran does not change the recalculated amounts. * Two callers can each receive 202 for the same session. Only one recalculation takes effect; the other is skipped when it runs - because another recalculation holds the per-session lock or billing has already completed - and is recorded as a failed action audit record.",
+      "tags": [
+        "action / session"
+      ],
+      "requestBody": {
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "reason": {
+                  "type": "string",
+                  "maxLength": 1000,
+                  "description": "Reason for recalculating the session, recorded on the session edit log."
+                }
+              }
+            }
+          }
+        }
+      },
+      "responses": {
+        "202": {
+          "description": "Action accepted. The session has been queued for recalculation."
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "409": {
+          "description": "Conflict - The request cannot be completed due to a conflict with the current state of the session. Possible errors: * `billingStatus` is already `completed` * Billing for this session is owned by the upstream roaming partner * The session `status` does not allow recalculation: it is neither `finished`, nor `pending` or `active` for a session that is already underway at the charge point * The required StartTransaction message was not found in the communication logs"
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "423": {
+          "description": "Locked - The session is temporarily locked because billing is being processed for it, or because a recalculation is already running. Retry later."
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/actions/session/v1.0/{session}/resume-billing",
+      "method": "POST",
+      "operationId": "sessionResumeBilling",
+      "summary": "Session / Resume billing",
+      "description": "Resume billing for a session whose billing was suspended by a failed validation rule, completing it either with the session amounts as they are or as a free session. The action runs as the token owner, who is recorded on the session edit log and on the action audit record. Requires the `Sessions.resume-billing` permission - a token whose admin does not hold it is rejected with 403, and so is a request for a session that belongs to another operator. An unknown session ID is rejected with 404. Preconditions, with the response code each failure produces: * `billingStatus` is `suspended` - otherwise 409 * The session is no longer underway at the charge point - otherwise 409. Not every `pending` or `active` session is rejected: a `pending` session that has not been sent to the charge point yet, and an `active` session that has stopped and is waiting for the cable to be unlocked, are not underway and are accepted. * Billing for the session is not owned by the upstream roaming partner - otherwise 409 * For `free_session`: the session has no order yet, unless the platform settings allow marking a session that already has an order as free - otherwise 409 * No recalculation is running for the session and the session is not locked for billing processing - otherwise 423 * `type` holds one of the documented values and `reason` is at most 1000 characters - otherwise 422 The validation rules are not re-run, so both `type` values end with `billingStatus` set to `completed`: `bill_as_is` keeps the session amounts and charging periods as they are, and `free_session` zeroes the amount charged to the driver first. This action cannot leave the session `suspended`. When billing cannot be completed after every precondition has passed, the session is left untouched and the action answers 409.",
+      "tags": [
+        "action / session"
+      ],
+      "requestBody": {
+        "required": true,
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "type": {
+                  "type": "string",
+                  "enum": [
+                    "bill_as_is",
+                    "free_session"
+                  ],
+                  "example": "bill_as_is",
+                  "description": "How billing is resumed for a session whose billing is suspended: - **bill_as_is**: Complete billing with the session amounts exactly as they are, leaving the charging periods untouched - **free_session**: Mark the session as free, which zeroes the amount charged to the driver, and then complete billing. This is irreversible - the amount the driver would have been charged is kept only as the session's previous total amount for audit purposes and cannot be restored by another action"
+                },
+                "reason": {
+                  "type": "string",
+                  "maxLength": 1000,
+                  "description": "Reason for resuming billing, recorded on the session edit log."
+                }
+              },
+              "required": [
+                "type"
+              ]
+            }
+          }
+        }
+      },
+      "responses": {
+        "202": {
+          "description": "Action accepted. Billing for the session has been resumed."
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "409": {
+          "description": "Conflict - The request cannot be completed due to a conflict with the current state of the session. Possible errors: * `billingStatus` is not `suspended` * The session is still underway at the charge point * Billing for this session is owned by the upstream roaming partner * The session already has an order and cannot be marked as free * Billing could not be resumed"
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "423": {
+          "description": "Locked - The session is temporarily locked because billing is being processed for it, or because a recalculation is already running. Retry later."
+        },
         "429": {
           "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
         }
@@ -5046,7 +5322,7 @@
       "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.",
+      "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. Send a JSON object containing the required `customFields` object. Omitted identifiers remain unchanged, while `null` clears the corresponding value. When custom fields are enabled for sessions, an empty object succeeds as a no-op. Invalid or unavailable identifiers, invalid values, and disabled custom fields return `422` validation errors, and no submitted values are changed. A `404` response means the session was not found.",
       "tags": [
         "action / session"
       ],
@@ -6171,7 +6447,7 @@
       "method": "POST",
       "operationId": "userCancelSubscription",
       "summary": "User / Cancel subscription",
-      "description": "Cancel a subscription to a user",
+      "description": "Cancels renewal of the user's subscription. The subscription and its benefits remain active until the current billing period ends. Use the terminate subscription action when benefits must end immediately.",
       "tags": [
         "action / user"
       ],
@@ -6457,6 +6733,59 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/users/v1.0/{user}/terminate-subscription",
+      "method": "POST",
+      "operationId": "userTerminateSubscription",
+      "summary": "User / Terminate subscription",
+      "description": "Permanently terminates the user's current subscription. This action is irreversible and any outstanding collection is processed asynchronously.",
+      "tags": [
+        "action / user"
+      ],
+      "requestBody": {
+        "required": true,
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "reason": {
+                  "type": "string",
+                  "maxLength": 255,
+                  "description": "The reason for the termination."
+                }
+              },
+              "required": [
+                "reason"
+              ]
+            }
+          }
+        }
+      },
+      "responses": {
+        "202": {
+          "description": "Action accepted"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "409": {
+          "description": "The subscription cannot be terminated in its current state"
+        },
+        "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/users/v2.0/{user}/export-all-private-data",
       "method": "GET",
@@ -8471,11 +8800,15 @@
                             "chaoji",
                             "nema-6-30",
                             "nema-6-50",
+                            "nema-10-30",
+                            "nema-10-50",
+                            "nema-14-30",
+                            "nema-14-50",
                             "mcs",
                             "unknown"
                           ],
                           "nullable": true,
-                          "description": "Type of connector available on the EVSE: - **type1**: Type 1 connector (SAE J1772 AC) - **type2**: Type 2 connector (IEC 62196-2 AC) - **type3**: Type 3 connector (IEC 62196-2 AC) - **chademo**: CHAdeMO DC fast charging - **ccs1**: Combined Charging System 1 (CCS1/Combo 1) - **ccs2**: Combined Charging System 2 (CCS2/Combo 2) - **schuko**: Standard European household socket - **nacs**: North American Charging Standard (Tesla) - **cee16**: CEE 16A industrial connector - **cee32**: CEE 32A industrial connector - **j1772**: SAE J1772 connector - **inductive**: Inductive/wireless charging - **nema-5-20**: Domestic M NEMA 5-20 Socket - **type-e-french**: French Type E socket - **type-g-british**: British Type G socket - **type-j-swiss**: Swiss Type J socket - **avcon**: AVCON connector (Australian standard) - **gb-t-ac**: GB/T AC connector (Chinese standard) - **gb-t-dc**: GB/T DC connector (Chinese standard) - **chaoji**: ChaoJi (CHAdeMO 3.0) - **nema-6-30**: NEMA 6-30 - **nema-6-50**: NEMA 6-50 - **mcs**: Megawatt Charging System (MCS) - **unknown**: Connector standard supplied by a 2.3.0+ OCPI roaming peer that is not part of the platform's recognised set. The original peer-supplied value is preserved internally and emitted on outbound OCPI flows."
+                          "description": "Type of connector available on the EVSE: - **type1**: Type 1 connector (SAE J1772 AC) - **type2**: Type 2 connector (IEC 62196-2 AC) - **type3**: Type 3 connector (IEC 62196-2 AC) - **chademo**: CHAdeMO DC fast charging - **ccs1**: Combined Charging System 1 (CCS1/Combo 1) - **ccs2**: Combined Charging System 2 (CCS2/Combo 2) - **schuko**: Standard European household socket - **nacs**: North American Charging Standard (Tesla) - **cee16**: CEE 16A industrial connector - **cee32**: CEE 32A industrial connector - **j1772**: SAE J1772 connector - **inductive**: Inductive/wireless charging - **nema-5-20**: Domestic M NEMA 5-20 Socket - **type-e-french**: French Type E socket - **type-g-british**: British Type G socket - **type-j-swiss**: Swiss Type J socket - **avcon**: AVCON connector (Australian standard) - **gb-t-ac**: GB/T AC connector (Chinese standard) - **gb-t-dc**: GB/T DC connector (Chinese standard) - **chaoji**: ChaoJi (CHAdeMO 3.0) - **nema-6-30**: NEMA 6-30 - **nema-6-50**: NEMA 6-50 - **nema-10-30**: NEMA 10-30 - **nema-10-50**: NEMA 10-50 - **nema-14-30**: NEMA 14-30 - **nema-14-50**: NEMA 14-50 - **mcs**: Megawatt Charging System (MCS) - **unknown**: Connector standard supplied by a 2.3.0+ OCPI roaming peer that is not part of the platform's recognised set. The original peer-supplied value is preserved internally and emitted on outbound OCPI flows."
                         }
                       },
                       "description": "Criteria for automatic EVSE selection based on technical requirements. Ignored when evseId is explicitly provided. Response behavior: Only present when EVSE criteria were specified in the request. Omitted when evseId was provided or no criteria were specified."
@@ -12561,10 +12894,14 @@
                     "chaoji",
                     "nema-6-30",
                     "nema-6-50",
+                    "nema-10-30",
+                    "nema-10-50",
+                    "nema-14-30",
+                    "nema-14-50",
                     "mcs",
                     "unknown"
                   ],
-                  "description": "Type of connector available on the EVSE: - **type1**: Type 1 connector (SAE J1772 AC) - **type2**: Type 2 connector (IEC 62196-2 AC) - **type3**: Type 3 connector (IEC 62196-2 AC) - **chademo**: CHAdeMO DC fast charging - **ccs1**: Combined Charging System 1 (CCS1/Combo 1) - **ccs2**: Combined Charging System 2 (CCS2/Combo 2) - **schuko**: Standard European household socket - **nacs**: North American Charging Standard (Tesla) - **cee16**: CEE 16A industrial connector - **cee32**: CEE 32A industrial connector - **j1772**: SAE J1772 connector - **inductive**: Inductive/wireless charging - **nema-5-20**: Domestic M NEMA 5-20 Socket - **type-e-french**: French Type E socket - **type-g-british**: British Type G socket - **type-j-swiss**: Swiss Type J socket - **avcon**: AVCON connector (Australian standard) - **gb-t-ac**: GB/T AC connector (Chinese standard) - **gb-t-dc**: GB/T DC connector (Chinese standard) - **chaoji**: ChaoJi (CHAdeMO 3.0) - **nema-6-30**: NEMA 6-30 - **nema-6-50**: NEMA 6-50 - **mcs**: Megawatt Charging System (MCS) - **unknown**: Connector standard supplied by a 2.3.0+ OCPI roaming peer that is not part of the platform's recognised set. The original peer-supplied value is preserved internally and emitted on outbound OCPI flows."
+                  "description": "Type of connector available on the EVSE: - **type1**: Type 1 connector (SAE J1772 AC) - **type2**: Type 2 connector (IEC 62196-2 AC) - **type3**: Type 3 connector (IEC 62196-2 AC) - **chademo**: CHAdeMO DC fast charging - **ccs1**: Combined Charging System 1 (CCS1/Combo 1) - **ccs2**: Combined Charging System 2 (CCS2/Combo 2) - **schuko**: Standard European household socket - **nacs**: North American Charging Standard (Tesla) - **cee16**: CEE 16A industrial connector - **cee32**: CEE 32A industrial connector - **j1772**: SAE J1772 connector - **inductive**: Inductive/wireless charging - **nema-5-20**: Domestic M NEMA 5-20 Socket - **type-e-french**: French Type E socket - **type-g-british**: British Type G socket - **type-j-swiss**: Swiss Type J socket - **avcon**: AVCON connector (Australian standard) - **gb-t-ac**: GB/T AC connector (Chinese standard) - **gb-t-dc**: GB/T DC connector (Chinese standard) - **chaoji**: ChaoJi (CHAdeMO 3.0) - **nema-6-30**: NEMA 6-30 - **nema-6-50**: NEMA 6-50 - **nema-10-30**: NEMA 10-30 - **nema-10-50**: NEMA 10-50 - **nema-14-30**: NEMA 14-30 - **nema-14-50**: NEMA 14-50 - **mcs**: Megawatt Charging System (MCS) - **unknown**: Connector standard supplied by a 2.3.0+ OCPI roaming peer that is not part of the platform's recognised set. The original peer-supplied value is preserved internally and emitted on outbound OCPI flows."
                 },
                 "format": {
                   "type": "string",
@@ -12704,10 +13041,14 @@
                     "chaoji",
                     "nema-6-30",
                     "nema-6-50",
+                    "nema-10-30",
+                    "nema-10-50",
+                    "nema-14-30",
+                    "nema-14-50",
                     "mcs",
                     "unknown"
                   ],
-                  "description": "Type of connector available on the EVSE: - **type1**: Type 1 connector (SAE J1772 AC) - **type2**: Type 2 connector (IEC 62196-2 AC) - **type3**: Type 3 connector (IEC 62196-2 AC) - **chademo**: CHAdeMO DC fast charging - **ccs1**: Combined Charging System 1 (CCS1/Combo 1) - **ccs2**: Combined Charging System 2 (CCS2/Combo 2) - **schuko**: Standard European household socket - **nacs**: North American Charging Standard (Tesla) - **cee16**: CEE 16A industrial connector - **cee32**: CEE 32A industrial connector - **j1772**: SAE J1772 connector - **inductive**: Inductive/wireless charging - **nema-5-20**: Domestic M NEMA 5-20 Socket - **type-e-french**: French Type E socket - **type-g-british**: British Type G socket - **type-j-swiss**: Swiss Type J socket - **avcon**: AVCON connector (Australian standard) - **gb-t-ac**: GB/T AC connector (Chinese standard) - **gb-t-dc**: GB/T DC connector (Chinese standard) - **chaoji**: ChaoJi (CHAdeMO 3.0) - **nema-6-30**: NEMA 6-30 - **nema-6-50**: NEMA 6-50 - **mcs**: Megawatt Charging System (MCS) - **unknown**: Connector standard supplied by a 2.3.0+ OCPI roaming peer that is not part of the platform's recognised set. The original peer-supplied value is preserved internally and emitted on outbound OCPI flows."
+                  "description": "Type of connector available on the EVSE: - **type1**: Type 1 connector (SAE J1772 AC) - **type2**: Type 2 connector (IEC 62196-2 AC) - **type3**: Type 3 connector (IEC 62196-2 AC) - **chademo**: CHAdeMO DC fast charging - **ccs1**: Combined Charging System 1 (CCS1/Combo 1) - **ccs2**: Combined Charging System 2 (CCS2/Combo 2) - **schuko**: Standard European household socket - **nacs**: North American Charging Standard (Tesla) - **cee16**: CEE 16A industrial connector - **cee32**: CEE 32A industrial connector - **j1772**: SAE J1772 connector - **inductive**: Inductive/wireless charging - **nema-5-20**: Domestic M NEMA 5-20 Socket - **type-e-french**: French Type E socket - **type-g-british**: British Type G socket - **type-j-swiss**: Swiss Type J socket - **avcon**: AVCON connector (Australian standard) - **gb-t-ac**: GB/T AC connector (Chinese standard) - **gb-t-dc**: GB/T DC connector (Chinese standard) - **chaoji**: ChaoJi (CHAdeMO 3.0) - **nema-6-30**: NEMA 6-30 - **nema-6-50**: NEMA 6-50 - **nema-10-30**: NEMA 10-30 - **nema-10-50**: NEMA 10-50 - **nema-14-30**: NEMA 14-30 - **nema-14-50**: NEMA 14-50 - **mcs**: Megawatt Charging System (MCS) - **unknown**: Connector standard supplied by a 2.3.0+ OCPI roaming peer that is not part of the platform's recognised set. The original peer-supplied value is preserved internally and emitted on outbound OCPI flows."
                 },
                 "format": {
                   "type": "string",
@@ -23098,10 +23439,14 @@
                               "chaoji",
                               "nema-6-30",
                               "nema-6-50",
+                              "nema-10-30",
+                              "nema-10-50",
+                              "nema-14-30",
+                              "nema-14-50",
                               "mcs",
                               "unknown"
                             ],
-                            "description": "Type of connector available on the EVSE: - **type1**: Type 1 connector (SAE J1772 AC) - **type2**: Type 2 connector (IEC 62196-2 AC) - **type3**: Type 3 connector (IEC 62196-2 AC) - **chademo**: CHAdeMO DC fast charging - **ccs1**: Combined Charging System 1 (CCS1/Combo 1) - **ccs2**: Combined Charging System 2 (CCS2/Combo 2) - **catarc**: CATARC connector (Chinese standard) - **schuko**: Standard European household socket - **nacs**: North American Charging Standard (Tesla) - **cee16**: CEE 16A industrial connector - **cee32**: CEE 32A industrial connector - **j1772**: SAE J1772 connector - **inductive**: Inductive/wireless charging - **nema-5-20**: Domestic M NEMA 5-20 Socket - **type-e-french**: French Type E socket - **type-g-british**: British Type G socket - **type-j-swiss**: Swiss Type J socket - **avcon**: AVCON connector (Australian standard) - **chaoji**: ChaoJi (CHAdeMO 3.0) - **nema-6-30**: NEMA 6-30 - **nema-6-50**: NEMA 6-50 - **mcs**: Megawatt Charging System (MCS) - **unknown**: Connector standard supplied by a 2.3.0+ OCPI roaming peer that is not part of the platform's recognised set. The original peer-supplied value is preserved internally and emitted on outbound OCPI flows."
+                            "description": "Type of connector available on the EVSE: - **type1**: Type 1 connector (SAE J1772 AC) - **type2**: Type 2 connector (IEC 62196-2 AC) - **type3**: Type 3 connector (IEC 62196-2 AC) - **chademo**: CHAdeMO DC fast charging - **ccs1**: Combined Charging System 1 (CCS1/Combo 1) - **ccs2**: Combined Charging System 2 (CCS2/Combo 2) - **catarc**: CATARC connector (Chinese standard) - **schuko**: Standard European household socket - **nacs**: North American Charging Standard (Tesla) - **cee16**: CEE 16A industrial connector - **cee32**: CEE 32A industrial connector - **j1772**: SAE J1772 connector - **inductive**: Inductive/wireless charging - **nema-5-20**: Domestic M NEMA 5-20 Socket - **type-e-french**: French Type E socket - **type-g-british**: British Type G socket - **type-j-swiss**: Swiss Type J socket - **avcon**: AVCON connector (Australian standard) - **chaoji**: ChaoJi (CHAdeMO 3.0) - **nema-6-30**: NEMA 6-30 - **nema-6-50**: NEMA 6-50 - **nema-10-30**: NEMA 10-30 - **nema-10-50**: NEMA 10-50 - **nema-14-30**: NEMA 14-30 - **nema-14-50**: NEMA 14-50 - **mcs**: Megawatt Charging System (MCS) - **unknown**: Connector standard supplied by a 2.3.0+ OCPI roaming peer that is not part of the platform's recognised set. The original peer-supplied value is preserved internally and emitted on outbound OCPI flows."
                           },
                           {
                             "type": "string",
@@ -27696,7 +28041,7 @@
                     "non_issue"
                   ],
                   "example": "investigating",
-                  "description": "Issue status: - **auto_recovery_in_progress**: Issue is in automatic recovery process (preparation state) - **information_collection_in_progress**: System is collecting diagnostic information (preparation state) - **new**: Issue has been reported and not yet investigated (open state) - **investigating**: Issue is currently being investigated (open state) - **resolution_in_progress**: Resolution actions are being applied (open state) - **resolved**: Issue has been resolved successfully (closed state) - **wont_fix**: Issue will not be fixed (closed state) - **non_issue**: Reported issue determined to not be an actual issue (closed state)"
+                  "description": "Issue status: - **auto_recovery_in_progress**: Issue is in automatic recovery process (preparation state) - **information_collection_in_progress**: **Deprecated.** Retained for backward compatibility only. Never emitted by the platform and rejected with a validation error when set via the API. - **new**: Issue has been reported and not yet investigated (open state) - **investigating**: Issue is currently being investigated (open state) - **resolution_in_progress**: Resolution actions are being applied (open state) - **resolved**: Issue has been resolved successfully (closed state) - **wont_fix**: Issue will not be fixed (closed state) - **non_issue**: Reported issue determined to not be an actual issue (closed state)"
                 },
                 "workflowState": {
                   "type": "string",
@@ -27827,7 +28172,7 @@
       "method": "POST",
       "operationId": "issuesCreate",
       "summary": "Issues / Create",
-      "description": "Create a new issue. Note - auto-resolution statuses (autoRecoveryInProgress, informationCollectionInProgress) cannot be set via API.",
+      "description": "Create a new issue. Note - the system-controlled status auto_recovery_in_progress cannot be set via API.",
       "tags": [
         "resource / issues"
       ],
@@ -27905,7 +28250,7 @@
                   ],
                   "default": "new",
                   "example": "investigating",
-                  "description": "Issue status: - **auto_recovery_in_progress**: Issue is in automatic recovery process (preparation state) - **information_collection_in_progress**: System is collecting diagnostic information (preparation state) - **new**: Issue has been reported and not yet investigated (open state) - **investigating**: Issue is currently being investigated (open state) - **resolution_in_progress**: Resolution actions are being applied (open state) - **resolved**: Issue has been resolved successfully (closed state) - **wont_fix**: Issue will not be fixed (closed state) - **non_issue**: Reported issue determined to not be an actual issue (closed state)"
+                  "description": "Issue status: - **auto_recovery_in_progress**: Issue is in automatic recovery process (preparation state) - **information_collection_in_progress**: **Deprecated.** Retained for backward compatibility only. Never emitted by the platform and rejected with a validation error when set via the API. - **new**: Issue has been reported and not yet investigated (open state) - **investigating**: Issue is currently being investigated (open state) - **resolution_in_progress**: Resolution actions are being applied (open state) - **resolved**: Issue has been resolved successfully (closed state) - **wont_fix**: Issue will not be fixed (closed state) - **non_issue**: Reported issue determined to not be an actual issue (closed state)"
                 },
                 "externalId": {
                   "type": "string",
@@ -27990,6 +28335,7 @@
       "parameters": {
         "query": {
           "include": {
+            "description": "**This parameter is deprecated. It has no effect because `relatedResources` is always returned.** Relations to include in the response.",
             "schema": {
               "type": "array",
               "items": {
@@ -28052,7 +28398,7 @@
       "method": "PATCH",
       "operationId": "issueUpdate",
       "summary": "Issue / Update",
-      "description": "Update an existing issue. Supports partial updates (PATCH semantics). Notes: - keyResource cannot be updated after creation - Cannot set auto-resolution statuses (autoRecoveryInProgress, informationCollectionInProgress) - When setting status to resolved, wontFix, or nonIssue, resolutionDetails is required",
+      "description": "Update an existing issue. Supports partial updates (PATCH semantics). Notes: - keyResource cannot be updated after creation - Cannot set the system-controlled status auto_recovery_in_progress - When setting status to resolved, wontFix, or nonIssue, resolutionDetails is required",
       "tags": [
         "resource / issues"
       ],
@@ -28085,7 +28431,7 @@
                     "non_issue"
                   ],
                   "example": "investigating",
-                  "description": "Issue status: - **auto_recovery_in_progress**: Issue is in automatic recovery process (preparation state) - **information_collection_in_progress**: System is collecting diagnostic information (preparation state) - **new**: Issue has been reported and not yet investigated (open state) - **investigating**: Issue is currently being investigated (open state) - **resolution_in_progress**: Resolution actions are being applied (open state) - **resolved**: Issue has been resolved successfully (closed state) - **wont_fix**: Issue will not be fixed (closed state) - **non_issue**: Reported issue determined to not be an actual issue (closed state)"
+                  "description": "Issue status: - **auto_recovery_in_progress**: Issue is in automatic recovery process (preparation state) - **information_collection_in_progress**: **Deprecated.** Retained for backward compatibility only. Never emitted by the platform and rejected with a validation error when set via the API. - **new**: Issue has been reported and not yet investigated (open state) - **investigating**: Issue is currently being investigated (open state) - **resolution_in_progress**: Resolution actions are being applied (open state) - **resolved**: Issue has been resolved successfully (closed state) - **wont_fix**: Issue will not be fixed (closed state) - **non_issue**: Reported issue determined to not be an actual issue (closed state)"
                 },
                 "category": {
                   "type": "string",
@@ -38852,7 +39198,9 @@
                   "type": "string",
                   "enum": [
                     "en",
+                    "be",
                     "bg",
+                    "bn",
                     "mk",
                     "el",
                     "zh-CN",
@@ -38878,6 +39226,7 @@
                     "ms",
                     "cy",
                     "sr",
+                    "sw",
                     "fr",
                     "fr-MA",
                     "ro",
@@ -38903,10 +39252,12 @@
                     "ka",
                     "af",
                     "hi",
+                    "hy",
                     "de-CH",
                     "fr-CH",
                     "it-CH",
                     "en-GB",
+                    "mt",
                     "tl-PH"
                   ],
                   "description": "IETF language tag."
@@ -39657,7 +40008,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. 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."
+                  "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."
                 },
                 "externalId": {
                   "type": "string"
@@ -46633,11 +46984,8 @@
         "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"
+          "description": "The request contains invalid criteria, including malformed custom field filter values"
         },
         "429": {
           "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
@@ -49847,6 +50195,11 @@
                   "type": "string",
                   "format": "date",
                   "description": "Return records whose period overlaps on or before this 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. 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."
                 }
               }
             }
@@ -49906,7 +50259,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.",
+      "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.",
       "tags": [
         "resource / reimbursement reports"
       ],
@@ -49931,11 +50284,10 @@
                   "type": "string",
                   "enum": [
                     "company",
-                    "private",
                     "public"
                   ],
                   "example": "company",
-                  "description": "The home-charging reimbursement classification of the session: - **company**: The session is reimbursed as company charging. - **private**: The session is reimbursed as private charging. - **public**: The session is reimbursed as public charging."
+                  "description": "The reimbursement classification represented by a report: - **company**: The report has a partner payer. - **public**: The report has an operator payer."
                 },
                 "beneficiaryUserId": {
                   "type": "integer"
@@ -49961,6 +50313,11 @@
                   "type": "string",
                   "format": "date",
                   "description": "Return reports whose period overlaps on or before this date."
+                },
+                "customFields": {
+                  "type": "object",
+                  "additionalProperties": true,
+                  "description": "Map of administrator-defined custom field identifiers to filter values. Send each entry as `filter[customFields.<identifier>]`."
                 }
               }
             }
@@ -49980,6 +50337,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"
         },
@@ -52844,7 +53204,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. 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."
+                  "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."
                 }
               }
             }
@@ -52890,10 +53250,10 @@
           "description": "You do not have permission to perform the action"
         },
         "404": {
-          "description": "The requested custom field filter identifier is unavailable"
+          "description": "The record is not found"
         },
         "422": {
-          "description": "The request contains invalid criteria, including malformed or non-filterable custom field filters"
+          "description": "The request contains invalid criteria, including malformed custom field filter values"
         },
         "429": {
           "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
@@ -56917,8 +57277,10 @@
                     "canceled",
                     "expired",
                     "suspended",
-                    "pending"
-                  ]
+                    "pending",
+                    "terminated"
+                  ],
+                  "description": "Subscription status. - `active`: The subscription is active - `canceled`: The subscription was canceled - `expired`: The subscription has expired - `suspended`: The subscription is temporarily suspended - `pending`: The subscription is awaiting activation - `terminated`: The subscription was permanently terminated"
                 },
                 "statusChangedAfter": {
                   "type": "string",
@@ -72925,7 +73287,7 @@
   ],
   "info": {
     "title": "Public API",
-    "version": "3.253.1",
+    "version": "3.254.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": [
@@ -72939,18 +73301,18 @@
       }
     }
   ],
-  "buildTimestamp": "2026-09-25T15:24:04.216Z",
+  "buildTimestamp": "2026-09-28T11:57:42.237Z",
   "stats": {
-    "totalEndpoints": 651,
-    "originalSize": 6087577,
-    "optimizedSize": 1691324,
-    "reductionPercent": 72.22,
-    "buildDuration": 1140,
+    "totalEndpoints": 657,
+    "originalSize": 6140006,
+    "optimizedSize": 1714637,
+    "reductionPercent": 72.07,
+    "buildDuration": 1572,
     "responseSchemas": {
-      "total": 651,
-      "withSchemas": 651,
-      "totalSchemaSize": 3494283,
-      "averageSchemaSize": 5368
+      "total": 657,
+      "withSchemas": 657,
+      "totalSchemaSize": 3519465,
+      "averageSchemaSize": 5357
     }
   }
 }