@ampeco/public-api-mcp 3.256.1 → 3.257.1

package/dist/generated/endpoints.json

@@ -3389,6 +3389,60 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/id-tag/v1.0/{idTag}/set-custom-fields",
+      "method": "POST",
+      "operationId": "idTagSetCustomFields",
+      "summary": "ID tag / 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 an ID tag without changing any other ID tag properties. This action requires permission to view the ID tag and the `RfidTags.update-custom-fields` permission. Send a JSON object containing only the required `customFields` object. Additional body properties or query parameters return `422` validation errors. Omitted identifiers remain unchanged, while `null` clears the corresponding value. When custom fields are enabled for ID tags, an empty object succeeds as a no-op. Invalid or unavailable identifiers and invalid values return `422` validation errors, and no submitted values are changed. If custom fields are disabled for the tenant or ID tags, the action returns `412 Precondition Failed`. A `404` response means the ID tag was not found or is not accessible.",
+      "tags": [
+        "action / id tag"
+      ],
+      "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 ID tag's v2.0 read representation after applying the submitted values"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
     {
       "path": "/public-api/actions/installer-job/v1.0/{installerJob}/assign-charge-points",
       "method": "POST",
@@ -3511,6 +3565,60 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/installer-job/v1.0/{installerJob}/set-custom-fields",
+      "method": "POST",
+      "operationId": "installerJobSetCustomFieldsV1_0",
+      "summary": "Installer job / 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 an installer job without changing its status, assignments, other properties or timestamps. This action requires permission to view the installer job and the `InstallerJobs.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 installer jobs, an empty object succeeds as a no-op. Invalid or unavailable identifiers and invalid values return `422` validation errors. If custom fields are disabled for the tenant or installer jobs, the action returns `412 Precondition Failed`. Neither rejection changes submitted values. A `404` means the job is missing or inaccessible.",
+      "tags": [
+        "action / installer job"
+      ],
+      "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 installer job's default read representation after applying the submitted values"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
     {
       "path": "/public-api/actions/invoice/v1.0/{invoice}/update-external-id",
       "method": "POST",
@@ -3874,7 +3982,7 @@
       "method": "POST",
       "operationId": "partnerInvoiceIssueCreditNote",
       "summary": "Partner invoice / Issue credit note",
-      "description": "Issue a full credit note cancelling the given partner invoice. The credit note copies the original's seller, buyer, currency and payment terms, negates every line item, is marked paid, and references the cancelled invoice via `referenceId`. Only one credit note may exist per invoice. Issuing returns the linked settlement report to `ready_to_invoice`. Partial credit notes are not supported. Eligibility depends on the B2B invoice processor recorded on the invoice at issuance. An invoice generated through the built-in B2B invoice integration is eligible as soon as it is issued. An invoice generated through a processor that certifies documents with a fiscal authority is eligible only after the original document has been certified — until the document exists at the fiscal authority there is nothing to cancel. Use `fiscalization.status` on the single-invoice read to observe this: `pending` and `failed` mean not yet creditable, `certified` means the precondition is met. Certification is a necessary, not a sufficient, condition — the rare certified document with no recorded `fiscalization.referenceNumber` described under `fiscalization.status` stays ineligible and requires operator intervention. A `425` means the original document has not been certified with the fiscal authority yet, so there is nothing to cancel. Retry once `fiscalization.status` on the single-invoice read reaches `certified`.",
+      "description": "Issue a full credit note cancelling the given partner invoice. The credit note copies the original's seller, buyer, currency and payment terms, negates every line item, and references the cancelled invoice via `referenceId`. It is issued with `paymentStatus` `unpaid` and carries no `amountPaid` — credit notes do not track payments. Only one credit note may exist per invoice. Issuing returns the linked settlement report to `ready_to_invoice`. Partial credit notes are not supported. Eligibility depends on the B2B invoice processor recorded on the invoice at issuance. An invoice generated through the built-in B2B invoice integration is eligible as soon as it is issued. An invoice generated through a processor that certifies documents with a fiscal authority is eligible only after the original document has been certified — until the document exists at the fiscal authority there is nothing to cancel. Use `fiscalization.status` on the single-invoice read to observe this: `pending` and `failed` mean not yet creditable, `certified` means the precondition is met. Certification is a necessary, not a sufficient, condition — the rare certified document with no recorded `fiscalization.referenceNumber` described under `fiscalization.status` stays ineligible and requires operator intervention. A `425` means the original document has not been certified with the fiscal authority yet, so there is nothing to cancel. Retry once `fiscalization.status` on the single-invoice read reaches `certified`.",
       "tags": [
         "action / partner invoice"
       ],
@@ -3902,6 +4010,72 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/partner-invoice/v1.0/{partnerInvoice}/register-payment",
+      "method": "POST",
+      "operationId": "partnerInvoiceRegisterPayment",
+      "summary": "Partner invoice / Register payment",
+      "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. Register a payment against the given partner invoice. The entry is recorded as a settlement record linked to the invoice, the invoice's `amountPaid` is recomputed from all of its linked entries, and `paymentStatus` is re-derived as `unpaid`, `partially_paid` or `paid` from the recomputed total against `totalAmount.withTax`. The request body uses the same property names as the settlement record it creates — `date`, `paidAmount` and `note`, with `note` empty when omitted here. The record returned by the partner settlement report records endpoints additionally carries `partnerInvoiceId` pointing back to this invoice. A negative `paidAmount` is accepted and records a reversing entry, as long as the resulting total paid does not fall below zero. While a settlement report has at least one partner invoice, its settlement records can no longer be created, updated or deleted directly — register payments here instead. A `409` means the invoice is permanently ineligible or the entry is inconsistent with the invoice's current state: the invoice has already been credited, the target is itself a credit note, or the entry would drive the total amount paid below zero.",
+      "tags": [
+        "action / partner invoice"
+      ],
+      "requestBody": {
+        "required": true,
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "paidAmount": {
+                  "type": "number",
+                  "example": 120.5,
+                  "description": "Amount registered as paid, in the invoice's currency. Must not be zero. A negative value records a reversing entry and must not drive the total amount paid on the invoice below zero."
+                },
+                "date": {
+                  "type": "string",
+                  "format": "date",
+                  "example": "2026-03-04",
+                  "description": "Date on which the payment was made."
+                },
+                "note": {
+                  "type": "string",
+                  "maxLength": 255,
+                  "example": "Bank transfer ref 998812",
+                  "description": "Free-text note stored on the resulting settlement record. Optional; when omitted the settlement record is created with an empty note, which the records endpoints still return as `note`."
+                }
+              },
+              "required": [
+                "paidAmount",
+                "date"
+              ]
+            }
+          }
+        }
+      },
+      "responses": {
+        "202": {
+          "description": "Accepted - the response body contains the updated partner invoice"
+        },
+        "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 payment could not be registered against the partner invoice — the invoice has been credited, the target is itself a credit note, or the entry would drive the total amount paid below zero."
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
     {
       "path": "/public-api/actions/partner-invoice/v1.0/{partnerInvoice}/update-external-id",
       "method": "POST",
@@ -3988,7 +4162,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. 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.",
+      "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 and invalid values return `422` validation errors. If custom fields are disabled for the tenant or partner settlement reports, the action returns `412 Precondition Failed`. Neither rejection changes submitted values. 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"
       ],
@@ -4026,6 +4200,9 @@
         "404": {
           "description": "The record is not found"
         },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
         "422": {
           "description": "The payload you provided is invalid"
         },
@@ -4090,7 +4267,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 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.",
+      "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 and invalid values return `422` validation errors. If custom fields are disabled for the tenant or partners, the action returns `412 Precondition Failed`. Neither rejection changes submitted values. A `404` response means the partner was not found.",
       "tags": [
         "action / partner"
       ],
@@ -4128,6 +4305,9 @@
         "404": {
           "description": "The record is not found"
         },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
         "422": {
           "description": "The payload you provided is invalid"
         },
@@ -4141,7 +4321,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. 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.",
+      "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 and invalid values return `422` validation errors. If custom fields are disabled for the tenant or payment terminals, the action returns `412 Precondition Failed`. Neither rejection changes submitted values. A `404` response means the payment terminal was not found.",
       "tags": [
         "action / payment terminal"
       ],
@@ -4179,6 +4359,9 @@
         "404": {
           "description": "The record is not found"
         },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
         "422": {
           "description": "The payload you provided is invalid"
         },
@@ -4303,7 +4486,7 @@
       "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.",
+      "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 and invalid values return `422` validation errors. If custom fields are disabled for the tenant or reimbursement records, the action returns `412 Precondition Failed`. Neither rejection changes submitted values. A `404` response means the reimbursement record was not found.",
       "tags": [
         "action / reimbursement record"
       ],
@@ -4341,6 +4524,9 @@
         "404": {
           "description": "The record is not found"
         },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
         "422": {
           "description": "The payload you provided is invalid"
         },
@@ -4381,7 +4567,7 @@
       "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.",
+      "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 and succeeds as a no-op when custom fields are enabled. 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 or inapplicable identifiers and invalid values return a `422` error keyed as `customFields.<identifier>`. If custom fields are disabled for the tenant or reimbursement reports, the action returns `412 Precondition Failed`, even for an empty object. Neither rejection changes submitted values. 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"
       ],
@@ -4419,6 +4605,9 @@
         "404": {
           "description": "The record is not found"
         },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
         "422": {
           "description": "The payload you provided is invalid"
         },
@@ -5323,7 +5512,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. 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.",
+      "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 and invalid values return `422` validation errors. If custom fields are disabled for the tenant or sessions, the action returns `412 Precondition Failed`. Neither rejection changes submitted values. A `404` response means the session was not found.",
       "tags": [
         "action / session"
       ],
@@ -5361,6 +5550,9 @@
         "404": {
           "description": "The record is not found"
         },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
         "422": {
           "description": "The payload you provided is invalid"
         },
@@ -5429,6 +5621,114 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/tariff-group/v1.0/{tariffGroup}/set-custom-fields",
+      "method": "POST",
+      "operationId": "tariffGroupSetCustomFields",
+      "summary": "Tariff group / 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 tariff group without changing its tariffs or other properties. This action requires permission to view the tariff group and the `TariffGroups.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 tariff groups, an empty object succeeds as a no-op. Invalid or unavailable identifiers and invalid values return `422` validation errors. If custom fields are disabled for the tenant or tariff groups, the action returns `412 Precondition Failed`. Neither rejection changes submitted values. A `404` response means the tariff group was not found.",
+      "tags": [
+        "action / tariff group"
+      ],
+      "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 tariff group's v1.0 read representation after applying the submitted values"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/actions/tariff/v1.0/{tariff}/set-custom-fields",
+      "method": "POST",
+      "operationId": "tariffSetCustomFields",
+      "summary": "Tariff / 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 tariff without changing its pricing or other properties. This action requires permission to view the tariff and the `Tariffs.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 tariffs, an empty object succeeds as a no-op. Invalid or unavailable identifiers and invalid values return `422` validation errors. If custom fields are disabled for the tenant or tariffs, the action returns `412 Precondition Failed`. Neither rejection changes submitted values. A `404` response means the tariff was not found or its type is not exposed through the Public API.",
+      "tags": [
+        "action / tariff"
+      ],
+      "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 tariff's v1.0 read representation after applying the submitted values"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
     {
       "path": "/public-api/actions/tariffs/v2.0/{tariff}/set-tariff-display-information",
       "method": "POST",
@@ -6256,6 +6556,60 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/user-group/v1.0/{userGroup}/set-custom-fields",
+      "method": "POST",
+      "operationId": "userGroupSetCustomFields",
+      "summary": "User group / 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 user group without changing any other user group properties. This action requires permission to view the user group and the `UserGroups.update-custom-fields` permission. Send a JSON object containing only the required `customFields` object; other body properties and any query parameters return `422` validation errors. Omitted identifiers remain unchanged, while `null` clears the corresponding value. When custom fields are enabled for user groups, an empty object succeeds as a no-op without an audit event. Invalid or unavailable submitted identifiers and invalid values return `422` validation errors. If custom fields are disabled for the tenant or user groups, the action returns `412 Precondition Failed`. Neither rejection changes values or creates an audit event. A `404` response means the user group was not found or is not accessible.",
+      "tags": [
+        "action / user-group"
+      ],
+      "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 user group'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"
+        },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
     {
       "path": "/public-api/actions/user/v1.0/{user}/revoke-marketing-consent",
       "method": "POST",
@@ -6673,6 +7027,60 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/users/v1.0/{user}/set-custom-fields",
+      "method": "POST",
+      "operationId": "userSetCustomFieldsV1_0",
+      "summary": "User / 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 user without changing any other user properties. This action requires permission to view the user and the `Users.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 user, the current custom field configuration and the acting administrator's access. Invalid request bodies or values and unknown or unusable submitted field identifiers return `422` validation errors, keyed as `customFields.<identifier>` for invalid identifiers. If custom fields are disabled for the tenant or users, the action returns `412 Precondition Failed`. Neither rejection changes custom field values.",
+      "tags": [
+        "action / user"
+      ],
+      "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 user's default v1.1 read representation after applying the submitted values"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
     {
       "path": "/public-api/actions/users/v1.0/{user}/subscribe-to-plan",
       "method": "POST",
@@ -6920,6 +7328,60 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/vehicle/v1.0/{vehicle}/set-custom-fields",
+      "method": "POST",
+      "operationId": "vehicleSetCustomFieldsV1_0",
+      "summary": "Vehicle / 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 vehicle without changing any other vehicle properties. This action requires permission to view the vehicle and the `Vehicles.update-custom-fields` permission. Send a JSON object containing only the required `customFields` property. Query parameters and additional body properties are rejected. When custom fields are enabled for vehicles, the `customFields` object may be empty and succeeds as a no-op without creating a value audit. Omitted identifiers remain unchanged, while an explicit `null` clears the corresponding value. Every submitted identifier is validated against the vehicle, the current custom field configuration and the acting administrator's access. Unknown, inaccessible, inapplicable or currently disabled identifiers return `422` validation errors keyed as `customFields.<identifier>`. If custom fields are disabled for the tenant or for vehicles, the action returns `412 Precondition Failed` and changes no submitted values. Malformed request bodies and invalid values for available fields return `422` validation errors keyed to the relevant request property. No submitted values are changed when the action is rejected. A `404` response means the vehicle was not found or is not accessible to the caller.",
+      "tags": [
+        "action / vehicle"
+      ],
+      "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 vehicle's default single-record v1.0 read representation after applying the submitted values"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "412": {
+          "description": "A precondition for performing this action is not met. The response message states which precondition failed."
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
     {
       "path": "/public-api/logs/communication/v1.0",
       "method": "GET",
@@ -17351,10 +17813,11 @@
                       "marketing",
                       "signup",
                       "subscription",
-                      "top-up"
+                      "top-up",
+                      "analytics"
                     ]
                   },
-                  "description": "Filter by term types: - marketing: Marketing and promotional communications consent - signup: Initial registration terms and conditions - subscription: Subscription service terms - top-up: Top-up service terms"
+                  "description": "Filter by term types: - marketing: Marketing and promotional communications consent - signup: Initial registration terms and conditions - subscription: Subscription service terms - top-up: Top-up service terms - analytics: Analytics data collection consent"
                 },
                 "action": {
                   "type": "array",
@@ -17441,10 +17904,11 @@
                       "marketing",
                       "signup",
                       "subscription",
-                      "top-up"
+                      "top-up",
+                      "analytics"
                     ]
                   },
-                  "description": "Filter by term types: - marketing: Marketing and promotional communications consent - signup: Initial registration terms and conditions - subscription: Subscription service terms - top-up: Top-up service terms"
+                  "description": "Filter by term types: - marketing: Marketing and promotional communications consent - signup: Initial registration terms and conditions - subscription: Subscription service terms - top-up: Top-up service terms - analytics: Analytics data collection consent"
                 },
                 "status": {
                   "type": "array",
@@ -25916,6 +26380,7 @@
             "type": "string"
           },
           "filter": {
+            "description": "Filter ID tags by standard properties or administrator-defined custom fields. Send a scalar under a literal dotted key, for example `filter[customFields.fleetLabel]=North`. Text, email and URL fields match substrings; boolean fields accept `true`, `false`, `1` or `0`. For number, date and date-time fields, send inclusive bounds under the dotted key, for example `filter[customFields.fleetNumber][from]=10&filter[customFields.fleetNumber][to]=20`. Either bound may be omitted. Multiple criteria combine with AND. Unfilled criteria are ignored. Non-empty unknown, inaccessible, disabled or unfilterable custom-field keys return `400`; malformed values for usable fields return `422`. Operator-scoped fields match only ID tags whose current operator is assigned to the field. Custom-field filters are applied before pagination. URL-encode query keys and values when sending the request.",
             "schema": {
               "type": "object",
               "properties": {
@@ -26007,6 +26472,11 @@
                   "type": "string",
                   "format": "date-time",
                   "description": "ISO 8601 formatted date. Lists only the id tags that were last updated on and before this datetime"
+                },
+                "customFields": {
+                  "type": "object",
+                  "additionalProperties": true,
+                  "description": "Filter a resource listing by administrator-defined custom fields using literal dotted keys such as `filter[customFields.reference]=INV-42`, not nested `filter[customFields][reference]` keys. Text, email and URL fields accept a single string and use case- and accent-insensitive substring matching; `%`, `_` and backslashes are matched literally. Boolean fields accept `true`, `false`, `1` or `0` as strings, or boolean and integer equivalents. Number, date and date-time fields accept inclusive `filter[customFields.<identifier>][from]` and/or `filter[customFields.<identifier>][to]` bounds, including one-sided ranges. Number bounds are decimal strings from `-99999999999999.999999` to `99999999999999.999999` with at most six fractional places, compared without rounding. Dates use `YYYY-MM-DD` calendar dates; date-times use ISO 8601, with offsets normalized to UTC and no offset interpreted as UTC. Long text and JSON fields are not filterable. Custom-field criteria combine with each other and the resource's other filters using AND. Empty criteria have no effect. Malformed values for usable fields return a property-bound `422` validation error. See each listing operation for how it handles unsupported nonempty criteria."
                 }
               }
             }
@@ -26017,6 +26487,9 @@
         "200": {
           "description": "Success"
         },
+        "400": {
+          "description": "Bad Request"
+        },
         "401": {
           "description": "Access token is missing or invalid"
         },
@@ -27581,6 +28054,11 @@
                   "type": "string",
                   "format": "date-time",
                   "description": "Lists the installer jobs that have been last updated before the specified date and time, please provide the value as an ISO 8601 formatted date"
+                },
+                "customFields": {
+                  "type": "object",
+                  "additionalProperties": true,
+                  "description": "Filter a resource listing by administrator-defined custom fields using literal dotted keys such as `filter[customFields.reference]=INV-42`, not nested `filter[customFields][reference]` keys. Text, email and URL fields accept a single string and use case- and accent-insensitive substring matching; `%`, `_` and backslashes are matched literally. Boolean fields accept `true`, `false`, `1` or `0` as strings, or boolean and integer equivalents. Number, date and date-time fields accept inclusive `filter[customFields.<identifier>][from]` and/or `filter[customFields.<identifier>][to]` bounds, including one-sided ranges. Number bounds are decimal strings from `-99999999999999.999999` to `99999999999999.999999` with at most six fractional places, compared without rounding. Dates use `YYYY-MM-DD` calendar dates; date-times use ISO 8601, with offsets normalized to UTC and no offset interpreted as UTC. Long text and JSON fields are not filterable. Custom-field criteria combine with each other and the resource's other filters using AND. Empty criteria have no effect. Malformed values for usable fields return a property-bound `422` validation error. See each listing operation for how it handles unsupported nonempty criteria."
                 }
               }
             }
@@ -27607,6 +28085,9 @@
         "200": {
           "description": "Success"
         },
+        "400": {
+          "description": "Bad Request"
+        },
         "401": {
           "description": "Access token is missing or invalid"
         },
@@ -35026,49 +35507,51 @@
                       "type": "number",
                       "format": "float",
                       "minimum": 0,
-                      "maximum": 100
+                      "maximum": 100,
+                      "description": "Applied to the session amount without tax, after any session fees and electricity cost are deducted."
                     },
                     "partnerSharePercentageDcEvse": {
                       "type": "number",
                       "format": "float",
                       "minimum": 0,
-                      "maximum": 100
+                      "maximum": 100,
+                      "description": "Applied to the session amount without tax, after any session fees and electricity cost are deducted."
                     },
                     "excludeConnectionFee": {
                       "type": "boolean",
-                      "description": "If the tariff has a Connection fee, this fee would not be included in the revenue sharing with the Partner and will remain entirely for the Operator."
+                      "description": "If true and the tariff has a connection fee, the partner receives no share of it and the operator keeps it in full. The connection fee excluded is the amount without tax."
                     },
                     "deductElectricityCost": {
                       "type": "boolean",
-                      "description": "The cost of the electricity would first be deducted from the collected revenue and then the Revenue sharing rules will be applied."
+                      "description": "The electricity cost without tax is deducted from the session amount, together with the session fees, before the partner's share is calculated."
                     },
                     "reimburseForElectricityCost": {
                       "type": "boolean",
-                      "description": "If set to true, the Partner would receive not only their share of the revenue but also a reimbursement for the cost of the electricity. The formula to calculate the amount to be received by the Partner is (Revenue - Electricity cost) x Partner percentage + Electricity cost. It could be supplied only if deductElectricityCost is set to true."
+                      "description": "If true, the partner also receives the electricity cost. The partner receives (Revenue − Deducted fees − Electricity cost) × Partner percentage + Electricity cost, where revenue and electricity cost are the amounts without tax and deducted fees are the fixed fee per session, the fee per kWh and the handling fee. It can be supplied only if `deductElectricityCost` is true."
                     },
                     "fixedFeePerSessionAc": {
                       "type": "number",
                       "format": "float",
                       "nullable": true,
-                      "description": "Additional flat fee that is applied for every billed session and subtracted from the Partner's share of the revenue for each session on AC Charging Station."
+                      "description": "Flat fee without tax for every billed session on an AC charge point. It is taken off the session amount before the partner's share is calculated, and the operator keeps it in full."
                     },
                     "fixedFeePerSessionDc": {
                       "type": "number",
                       "format": "float",
                       "nullable": true,
-                      "description": "Additional flat fee that is applied for every billed session and subtracted from the Partner's share of the revenue for each session on DC Charging Station."
+                      "description": "Flat fee without tax for every billed session on a DC charge point. It is taken off the session amount before the partner's share is calculated, and the operator keeps it in full."
                     },
                     "feePerKwhAc": {
                       "type": "number",
                       "format": "float",
                       "nullable": true,
-                      "description": "Additional flat fee that is applied for every billed kWh and subtracted from the Partner's share of the revenue for each kWh billed on AC Charging Station."
+                      "description": "Flat fee without tax for every billed kWh on an AC charge point. It is taken off the session amount before the partner's share is calculated, and the operator keeps it in full."
                     },
                     "feePerKwhDc": {
                       "type": "number",
                       "format": "float",
                       "nullable": true,
-                      "description": "Additional flat fee that is applied for every billed kWh and subtracted from the Partner's share of the revenue for each kWh billed on DC Charging Station."
+                      "description": "Flat fee without tax for every billed kWh on a DC charge point. It is taken off the session amount before the partner's share is calculated, and the operator keeps it in full."
                     },
                     "handlingFee": {
                       "type": "number",
@@ -35076,7 +35559,7 @@
                       "minimum": 0,
                       "maximum": 100,
                       "nullable": true,
-                      "description": "Additional percentage fee to be applied on the total amount paid by the user for the session. This fee is then subtracted from the Partner's share of the revenue."
+                      "description": "A percentage of the total amount the user paid for the session, including tax. It is taken off the session amount before the partner's share is calculated."
                     }
                   }
                 },
@@ -35086,17 +35569,17 @@
                     "perChargePoint": {
                       "type": "number",
                       "format": "float",
-                      "description": "The provided amount should be excluding VAT."
+                      "description": "The amount without tax."
                     },
                     "perAcEvse": {
                       "type": "number",
                       "format": "float",
-                      "description": "The provided amount should be excluding VAT."
+                      "description": "The amount without tax."
                     },
                     "perDcEvse": {
                       "type": "number",
                       "format": "float",
-                      "description": "The provided amount should be excluding VAT."
+                      "description": "The amount without tax."
                     }
                   }
                 },
@@ -35279,49 +35762,51 @@
                       "type": "number",
                       "format": "float",
                       "minimum": 0,
-                      "maximum": 100
+                      "maximum": 100,
+                      "description": "Applied to the session amount without tax, after any session fees and electricity cost are deducted."
                     },
                     "partnerSharePercentageDcEvse": {
                       "type": "number",
                       "format": "float",
                       "minimum": 0,
-                      "maximum": 100
+                      "maximum": 100,
+                      "description": "Applied to the session amount without tax, after any session fees and electricity cost are deducted."
                     },
                     "excludeConnectionFee": {
                       "type": "boolean",
-                      "description": "If the tariff has a Connection fee, this fee would not be included in the revenue sharing with the Partner and will remain entirely for the Operator."
+                      "description": "If true and the tariff has a connection fee, the partner receives no share of it and the operator keeps it in full. The connection fee excluded is the amount without tax."
                     },
                     "deductElectricityCost": {
                       "type": "boolean",
-                      "description": "The cost of the electricity would first be deducted from the collected revenue and then the Revenue sharing rules will be applied."
+                      "description": "The electricity cost without tax is deducted from the session amount, together with the session fees, before the partner's share is calculated."
                     },
                     "reimburseForElectricityCost": {
                       "type": "boolean",
-                      "description": "If set to true, the Partner would receive not only their share of the revenue but also a reimbursement for the cost of the electricity. The formula to calculate the amount to be received by the Partner is (Revenue - Electricity cost) x Partner percentage + Electricity cost. It could be supplied only if deductElectricityCost is set to true."
+                      "description": "If true, the partner also receives the electricity cost. The partner receives (Revenue − Deducted fees − Electricity cost) × Partner percentage + Electricity cost, where revenue and electricity cost are the amounts without tax and deducted fees are the fixed fee per session, the fee per kWh and the handling fee. It can be supplied only if `deductElectricityCost` is true."
                     },
                     "fixedFeePerSessionAc": {
                       "type": "number",
                       "format": "float",
                       "nullable": true,
-                      "description": "Additional flat fee that is applied for every billed session and subtracted from the Partner's share of the revenue for each session on AC Charging Station."
+                      "description": "Flat fee without tax for every billed session on an AC charge point. It is taken off the session amount before the partner's share is calculated, and the operator keeps it in full."
                     },
                     "fixedFeePerSessionDc": {
                       "type": "number",
                       "format": "float",
                       "nullable": true,
-                      "description": "Additional flat fee that is applied for every billed session and subtracted from the Partner's share of the revenue for each session on DC Charging Station."
+                      "description": "Flat fee without tax for every billed session on a DC charge point. It is taken off the session amount before the partner's share is calculated, and the operator keeps it in full."
                     },
                     "feePerKwhAc": {
                       "type": "number",
                       "format": "float",
                       "nullable": true,
-                      "description": "Additional flat fee that is applied for every billed kWh and subtracted from the Partner's share of the revenue for each kWh billed on AC Charging Station."
+                      "description": "Flat fee without tax for every billed kWh on an AC charge point. It is taken off the session amount before the partner's share is calculated, and the operator keeps it in full."
                     },
                     "feePerKwhDc": {
                       "type": "number",
                       "format": "float",
                       "nullable": true,
-                      "description": "Additional flat fee that is applied for every billed kWh and subtracted from the Partner's share of the revenue for each kWh billed on DC Charging Station."
+                      "description": "Flat fee without tax for every billed kWh on a DC charge point. It is taken off the session amount before the partner's share is calculated, and the operator keeps it in full."
                     },
                     "handlingFee": {
                       "type": "number",
@@ -35329,7 +35814,7 @@
                       "minimum": 0,
                       "maximum": 100,
                       "nullable": true,
-                      "description": "Additional percentage fee to be applied on the total amount paid by the user for the session. This fee is then subtracted from the Partner's share of the revenue."
+                      "description": "A percentage of the total amount the user paid for the session, including tax. It is taken off the session amount before the partner's share is calculated."
                     }
                   }
                 },
@@ -35339,17 +35824,17 @@
                     "perChargePoint": {
                       "type": "number",
                       "format": "float",
-                      "description": "The provided amount should be excluding VAT."
+                      "description": "The amount without tax."
                     },
                     "perAcEvse": {
                       "type": "number",
                       "format": "float",
-                      "description": "The provided amount should be excluding VAT."
+                      "description": "The amount without tax."
                     },
                     "perDcEvse": {
                       "type": "number",
                       "format": "float",
-                      "description": "The provided amount should be excluding VAT."
+                      "description": "The amount without tax."
                     }
                   }
                 },
@@ -35509,49 +35994,51 @@
                       "type": "number",
                       "format": "float",
                       "minimum": 0,
-                      "maximum": 100
+                      "maximum": 100,
+                      "description": "Applied to the session amount without tax, after any session fees and electricity cost are deducted."
                     },
                     "partnerSharePercentageDcEvse": {
                       "type": "number",
                       "format": "float",
                       "minimum": 0,
-                      "maximum": 100
+                      "maximum": 100,
+                      "description": "Applied to the session amount without tax, after any session fees and electricity cost are deducted."
                     },
                     "excludeConnectionFee": {
                       "type": "boolean",
-                      "description": "If the tariff has a Connection fee, this fee would not be included in the revenue sharing with the Partner and will remain entirely for the Operator."
+                      "description": "If true and the tariff has a connection fee, the partner receives no share of it and the operator keeps it in full. The connection fee excluded is the amount without tax."
                     },
                     "deductElectricityCost": {
                       "type": "boolean",
-                      "description": "The cost of the electricity would first be deducted from the collected revenue and then the Revenue sharing rules will be applied."
+                      "description": "The electricity cost without tax is deducted from the session amount, together with the session fees, before the partner's share is calculated."
                     },
                     "reimburseForElectricityCost": {
                       "type": "boolean",
-                      "description": "If set to true, the Partner would receive not only their share of the revenue but also a reimbursement for the cost of the electricity. The formula to calculate the amount to be received by the Partner is (Revenue - Electricity cost) x Partner percentage + Electricity cost. It could be supplied only if deductElectricityCost is set to true."
+                      "description": "If true, the partner also receives the electricity cost. The partner receives (Revenue − Deducted fees − Electricity cost) × Partner percentage + Electricity cost, where revenue and electricity cost are the amounts without tax and deducted fees are the fixed fee per session, the fee per kWh and the handling fee. It can be supplied only if `deductElectricityCost` is true."
                     },
                     "fixedFeePerSessionAc": {
                       "type": "number",
                       "format": "float",
                       "nullable": true,
-                      "description": "Additional flat fee that is applied for every billed session and subtracted from the Partner's share of the revenue for each session on AC Charging Station."
+                      "description": "Flat fee without tax for every billed session on an AC charge point. It is taken off the session amount before the partner's share is calculated, and the operator keeps it in full."
                     },
                     "fixedFeePerSessionDc": {
                       "type": "number",
                       "format": "float",
                       "nullable": true,
-                      "description": "Additional flat fee that is applied for every billed session and subtracted from the Partner's share of the revenue for each session on DC Charging Station."
+                      "description": "Flat fee without tax for every billed session on a DC charge point. It is taken off the session amount before the partner's share is calculated, and the operator keeps it in full."
                     },
                     "feePerKwhAc": {
                       "type": "number",
                       "format": "float",
                       "nullable": true,
-                      "description": "Additional flat fee that is applied for every billed kWh and subtracted from the Partner's share of the revenue for each kWh billed on AC Charging Station."
+                      "description": "Flat fee without tax for every billed kWh on an AC charge point. It is taken off the session amount before the partner's share is calculated, and the operator keeps it in full."
                     },
                     "feePerKwhDc": {
                       "type": "number",
                       "format": "float",
                       "nullable": true,
-                      "description": "Additional flat fee that is applied for every billed kWh and subtracted from the Partner's share of the revenue for each kWh billed on DC Charging Station."
+                      "description": "Flat fee without tax for every billed kWh on a DC charge point. It is taken off the session amount before the partner's share is calculated, and the operator keeps it in full."
                     },
                     "handlingFee": {
                       "type": "number",
@@ -35559,7 +36046,7 @@
                       "minimum": 0,
                       "maximum": 100,
                       "nullable": true,
-                      "description": "Additional percentage fee to be applied on the total amount paid by the user for the session. This fee is then subtracted from the Partner's share of the revenue."
+                      "description": "A percentage of the total amount the user paid for the session, including tax. It is taken off the session amount before the partner's share is calculated."
                     }
                   }
                 },
@@ -35569,17 +36056,17 @@
                     "perChargePoint": {
                       "type": "number",
                       "format": "float",
-                      "description": "The provided amount should be excluding VAT."
+                      "description": "The amount without tax."
                     },
                     "perAcEvse": {
                       "type": "number",
                       "format": "float",
-                      "description": "The provided amount should be excluding VAT."
+                      "description": "The amount without tax."
                     },
                     "perDcEvse": {
                       "type": "number",
                       "format": "float",
-                      "description": "The provided amount should be excluding VAT."
+                      "description": "The amount without tax."
                     }
                   }
                 },
@@ -35737,7 +36224,7 @@
                   "minimum": 0,
                   "maximum": 100,
                   "example": 70.5,
-                  "description": "Partner share percentage applied to AC sessions matched by this override. Omit to inherit the value from the partner contract. At least one of `acPercent` and `dcPercent` must be provided."
+                  "description": "Partner share percentage applied to AC sessions matched by this override. Applied to the session amount without tax, after any session fees and electricity cost are deducted. Omit to inherit the value from the partner contract. At least one of `acPercent` and `dcPercent` must be provided."
                 },
                 "dcPercent": {
                   "type": "number",
@@ -35745,7 +36232,7 @@
                   "minimum": 0,
                   "maximum": 100,
                   "example": 60,
-                  "description": "Partner share percentage applied to DC sessions matched by this override. Omit to inherit the value from the partner contract. At least one of `acPercent` and `dcPercent` must be provided."
+                  "description": "Partner share percentage applied to DC sessions matched by this override. Applied to the session amount without tax, after any session fees and electricity cost are deducted. Omit to inherit the value from the partner contract. At least one of `acPercent` and `dcPercent` must be provided."
                 }
               },
               "required": [
@@ -35908,7 +36395,7 @@
                   "maximum": 100,
                   "example": 70.5,
                   "nullable": true,
-                  "description": "Partner share percentage applied to AC sessions matched by this override. Send `null` to inherit the value from the partner contract. `acPercent` and `dcPercent` cannot both end up inherited."
+                  "description": "Partner share percentage applied to AC sessions matched by this override. Applied to the session amount without tax, after any session fees and electricity cost are deducted. Send `null` to inherit the value from the partner contract. `acPercent` and `dcPercent` cannot both end up inherited."
                 },
                 "dcPercent": {
                   "type": "number",
@@ -35917,7 +36404,7 @@
                   "maximum": 100,
                   "example": 60,
                   "nullable": true,
-                  "description": "Partner share percentage applied to DC sessions matched by this override. Send `null` to inherit the value from the partner contract. `acPercent` and `dcPercent` cannot both end up inherited."
+                  "description": "Partner share percentage applied to DC sessions matched by this override. Applied to the session amount without tax, after any session fees and electricity cost are deducted. Send `null` to inherit the value from the partner contract. `acPercent` and `dcPercent` cannot both end up inherited."
                 }
               },
               "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. Settlement override update schema. Omitted properties keep their current value; `restriction` is replaced as a whole when present."
@@ -39323,7 +39810,9 @@
                     "it-CH",
                     "en-GB",
                     "mt",
-                    "tl-PH"
+                    "tl-PH",
+                    "vi-VN",
+                    "sk"
                   ],
                   "description": "IETF language tag."
                 },
@@ -39660,7 +40149,7 @@
                     "paid"
                   ],
                   "example": "unpaid",
-                  "description": "Partner invoice payment status: - **unpaid**: No payment has been recorded against the invoice. - **partially_paid**: A payment has been recorded but the full amount is not yet covered. - **paid**: The full amount has been paid."
+                  "description": "Partner invoice payment status: - **unpaid**: `amountPaid` is zero or below and `totalAmount.withTax` is above zero — nothing has been registered against an invoice that has something to collect. - **partially_paid**: `amountPaid` is above zero but below `totalAmount.withTax`. - **paid**: `amountPaid` reaches or exceeds `totalAmount.withTax`. An invoice whose total is zero is `paid` from creation, with nothing registered against it, and an overpayment stays `paid`. These rules apply to documents with `type` `invoice`. A document with `type` `credit_note` always reports `unpaid` and never changes — payments are not tracked against credit notes."
                 },
                 "type": {
                   "type": "string",
@@ -40206,7 +40695,7 @@
       "method": "POST",
       "operationId": "partnerSettlementReportPartnerSettlementRecordCreate",
       "summary": "Partner Settlement Report / Partner Settlement Record / Create",
-      "description": "Create Partner Settlement Record",
+      "description": "Create Partner Settlement Record. A `409` with `errorCode` `payment_tracking_managed_via_partner_invoice` is returned once the settlement report has at least one partner invoice. From that point payments for the report are tracked by registering them on its partner invoices — use `POST actions/partner-invoice/v1.0/{partnerInvoice}/register-payment` instead. Listing and reading records stay available as read-only history.",
       "tags": [
         "resource / partner settlement reports"
       ],
@@ -40227,13 +40716,16 @@
               "properties": {
                 "date": {
                   "type": "string",
-                  "format": "date"
+                  "format": "date",
+                  "description": "Date the payment was made."
                 },
                 "paidAmount": {
-                  "type": "number"
+                  "type": "number",
+                  "description": "Amount recorded as paid, in the settlement report's currency. Negative values record a reversing entry."
                 },
                 "note": {
-                  "type": "string"
+                  "type": "string",
+                  "description": "Free-text note on the settlement record."
                 }
               },
               "required": [
@@ -40258,6 +40750,9 @@
         "404": {
           "description": "The record is not found"
         },
+        "409": {
+          "description": "The settlement record could not be written because the settlement report has at least one partner invoice. Payments for such a report are tracked by registering them on its partner invoices."
+        },
         "422": {
           "description": "The payload you provided is invalid"
         },
@@ -40310,7 +40805,7 @@
       "method": "PUT",
       "operationId": "partnerSettlementReportPartnerSettlementRecordUpdate",
       "summary": "Partner Settlement Report / Partner Settlement Record / Update",
-      "description": "Update a single Partner Settlement Record",
+      "description": "Update a single Partner Settlement Record. A `409` with `errorCode` `payment_tracking_managed_via_partner_invoice` is returned once the settlement report has at least one partner invoice. Records linked to an invoice are immutable history — correct a wrong entry by registering a reversing payment with a negative `paidAmount` through `POST actions/partner-invoice/v1.0/{partnerInvoice}/register-payment`.",
       "tags": [
         "resource / partner settlement reports"
       ],
@@ -40335,13 +40830,16 @@
               "properties": {
                 "date": {
                   "type": "string",
-                  "format": "date"
+                  "format": "date",
+                  "description": "Date the payment was made."
                 },
                 "paidAmount": {
-                  "type": "number"
+                  "type": "number",
+                  "description": "Amount recorded as paid, in the settlement report's currency. Negative values record a reversing entry."
                 },
                 "note": {
-                  "type": "string"
+                  "type": "string",
+                  "description": "Free-text note on the settlement record."
                 }
               },
               "required": [
@@ -40366,6 +40864,9 @@
         "404": {
           "description": "The record is not found"
         },
+        "409": {
+          "description": "The settlement record could not be written because the settlement report has at least one partner invoice. Payments for such a report are tracked by registering them on its partner invoices."
+        },
         "422": {
           "description": "The payload you provided is invalid"
         },
@@ -40379,7 +40880,7 @@
       "method": "DELETE",
       "operationId": "partnerSettlementReportPartnerSettlementRecordDelete",
       "summary": "Partner Settlement Report / Partner Settlement Record / Delete",
-      "description": "Delete a single Partner Settlement Record",
+      "description": "Delete a single Partner Settlement Record. A `409` with `errorCode` `payment_tracking_managed_via_partner_invoice` is returned once the settlement report has at least one partner invoice. Deleting would silently move the invoice's computed `amountPaid`, so corrections are made by registering a reversing payment with a negative `paidAmount` through `POST actions/partner-invoice/v1.0/{partnerInvoice}/register-payment` instead.",
       "tags": [
         "resource / partner settlement reports"
       ],
@@ -40408,6 +40909,9 @@
         "404": {
           "description": "The record is not found"
         },
+        "409": {
+          "description": "The settlement record could not be written because the settlement report has at least one partner invoice. Payments for such a report are tracked by registering them on its partner invoices."
+        },
         "422": {
           "description": "The payload you provided is invalid"
         },
@@ -47138,6 +47642,14 @@
                     "externalId": {
                       "type": "string",
                       "description": "An optional external identifier for the terminal that can be used to reference it in external systems."
+                    },
+                    "operationMode": {
+                      "type": "string",
+                      "enum": [
+                        "always_on",
+                        "plug_in_first"
+                      ],
+                      "description": "The active Payter payment terminal behavior: - **always_on**: The terminal keeps a preauthorized payment available while linked to a single charge point. - **plug_in_first**: The terminal starts the payment flow after a vehicle is plugged in."
                     }
                   },
                   "required": [
@@ -48635,6 +49147,14 @@
                     "externalId": {
                       "type": "string",
                       "description": "An optional external identifier for the terminal that can be used to reference it in external systems."
+                    },
+                    "operationMode": {
+                      "type": "string",
+                      "enum": [
+                        "always_on",
+                        "plug_in_first"
+                      ],
+                      "description": "The active Payter payment terminal behavior: - **always_on**: The terminal keeps a preauthorized payment available while linked to a single charge point. - **plug_in_first**: The terminal starts the payment flow after a vehicle is plugged in."
                     }
                   },
                   "oneOf": [
@@ -57471,7 +57991,7 @@
       "method": "GET",
       "operationId": "tariffGroupsListing",
       "summary": "Tariff Groups / Listing",
-      "description": "Get all tariff groups",
+      "description": "Get all tariff groups. Nonempty custom-field filter criteria for unknown, inaccessible, disabled, deleted or non-filterable fields return `400`. Malformed values for usable custom-field filters return `422`.",
       "tags": [
         "resource / tariffs"
       ],
@@ -57521,6 +58041,11 @@
                   "type": "string",
                   "format": "date-time",
                   "description": "ISO 8601 formatted date. Lists only the tariff groups that were created on and before this datetime"
+                },
+                "customFields": {
+                  "type": "object",
+                  "additionalProperties": true,
+                  "description": "Filter a resource listing by administrator-defined custom fields using literal dotted keys such as `filter[customFields.reference]=INV-42`, not nested `filter[customFields][reference]` keys. Text, email and URL fields accept a single string and use case- and accent-insensitive substring matching; `%`, `_` and backslashes are matched literally. Boolean fields accept `true`, `false`, `1` or `0` as strings, or boolean and integer equivalents. Number, date and date-time fields accept inclusive `filter[customFields.<identifier>][from]` and/or `filter[customFields.<identifier>][to]` bounds, including one-sided ranges. Number bounds are decimal strings from `-99999999999999.999999` to `99999999999999.999999` with at most six fractional places, compared without rounding. Dates use `YYYY-MM-DD` calendar dates; date-times use ISO 8601, with offsets normalized to UTC and no offset interpreted as UTC. Long text and JSON fields are not filterable. Custom-field criteria combine with each other and the resource's other filters using AND. Empty criteria have no effect. Malformed values for usable fields return a property-bound `422` validation error. See each listing operation for how it handles unsupported nonempty criteria."
                 }
               }
             }
@@ -57547,6 +58072,9 @@
         "200": {
           "description": "Success"
         },
+        "400": {
+          "description": "Bad Request"
+        },
         "401": {
           "description": "Access token is missing or invalid"
         },
@@ -57835,7 +58363,7 @@
       "method": "GET",
       "operationId": "tariffsListing",
       "summary": "Tariffs / Listing",
-      "description": "Get all tariff. Also you could use the `tariffGroupId` and the `userId` to \"resolve\" the concrete tariff within a group that would be applied to the specified user.",
+      "description": "Get all tariff. Also you could use the `tariffGroupId` and the `userId` to \"resolve\" the concrete tariff within a group that would be applied to the specified user. Nonempty custom-field filter criteria for unknown, inaccessible, disabled, deleted or non-filterable fields return `400`. Malformed values for usable custom-field filters return `422`.",
       "tags": [
         "resource / tariffs"
       ],
@@ -57890,6 +58418,11 @@
                   "type": "string",
                   "format": "date-time",
                   "description": "ISO 8601 formatted date. Lists only the tariffs that were last updated on and before this datetime"
+                },
+                "customFields": {
+                  "type": "object",
+                  "additionalProperties": true,
+                  "description": "Filter a resource listing by administrator-defined custom fields using literal dotted keys such as `filter[customFields.reference]=INV-42`, not nested `filter[customFields][reference]` keys. Text, email and URL fields accept a single string and use case- and accent-insensitive substring matching; `%`, `_` and backslashes are matched literally. Boolean fields accept `true`, `false`, `1` or `0` as strings, or boolean and integer equivalents. Number, date and date-time fields accept inclusive `filter[customFields.<identifier>][from]` and/or `filter[customFields.<identifier>][to]` bounds, including one-sided ranges. Number bounds are decimal strings from `-99999999999999.999999` to `99999999999999.999999` with at most six fractional places, compared without rounding. Dates use `YYYY-MM-DD` calendar dates; date-times use ISO 8601, with offsets normalized to UTC and no offset interpreted as UTC. Long text and JSON fields are not filterable. Custom-field criteria combine with each other and the resource's other filters using AND. Empty criteria have no effect. Malformed values for usable fields return a property-bound `422` validation error. See each listing operation for how it handles unsupported nonempty criteria."
                 }
               }
             }
@@ -57916,6 +58449,9 @@
         "200": {
           "description": "Success"
         },
+        "400": {
+          "description": "Bad Request"
+        },
         "401": {
           "description": "Access token is missing or invalid"
         },
@@ -64094,7 +64630,7 @@
       "method": "GET",
       "operationId": "transactionsListing",
       "summary": "Transactions / Listing",
-      "description": "Get all transactions. Nonempty custom-field filter criteria for unknown, inaccessible, disabled, deleted or non-filterable fields have no effect on this listing.",
+      "description": "Get all transactions. Nonempty custom-field filter criteria for unknown, inaccessible, disabled, deleted or non-filterable fields return `400`. Malformed values for usable custom-field filters return `422`.",
       "tags": [
         "resource / transactions"
       ],
@@ -65473,7 +66009,9 @@
                   "format": "date-time",
                   "description": "ISO 8601 formatted date. Lists only the user group records that were created on and before this datetime"
                 }
-              }
+              },
+              "additionalProperties": true,
+              "description": "Send custom field criteria as literal dotted keys `filter[customFields.<identifier>]`, not as nested `filter[customFields][<identifier>]` keys. Text, email, and URL fields accept a string matched as a case- and accent-insensitive substring, with `%`, `_`, and backslash treated literally. Boolean fields accept `true`, `false`, `1`, or `0`. Number, date, and date-time fields accept inclusive `filter[customFields.<identifier>][from]` and/or `filter[customFields.<identifier>][to]` bounds; when both are sent, `from` must not exceed `to`. Number bounds are decimal strings from `-99999999999999.999999` through `99999999999999.999999` with at most six fractional digits and no rounding. Date bounds are `YYYY-MM-DD` calendar dates. Date-time bounds are ISO 8601 timestamps: offsets are normalized to UTC and an absent offset means UTC. Multiple identifiers combine with AND. Blank or null scalar criteria and ranges with both bounds unfilled have no effect, including for unknown dotted keys. Populated criteria for unknown, deleted, restricted, operator-inapplicable, disabled, or non-filterable fields return `400`; malformed values for usable fields return `422`. Custom-field criteria never return `404`. Operator-scoped fields match only groups whose current operator owner makes the definition applicable."
             }
           },
           "page": {
@@ -65498,12 +66036,18 @@
         "200": {
           "description": "Success"
         },
+        "400": {
+          "description": "Bad Request"
+        },
         "401": {
           "description": "Access token is missing or invalid"
         },
         "403": {
           "description": "You do not have permission to perform the action"
         },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
         "429": {
           "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
         }
@@ -69471,6 +70015,7 @@
       "parameters": {
         "query": {
           "filter": {
+            "description": "Filter by user properties or applicable custom field values. For custom fields, add one extra top-level filter entry named `customFields.<identifier>` per criterion, for example `filter[customFields.invoiceReference]=INV-42`. Custom-field criteria combine with the user filters using AND. Operator-scoped criteria match only users whose current operator owner is assigned to the field; retained values from inapplicable definitions do not match. Non-empty unknown, inaccessible, disabled, deleted or non-filterable custom-field keys return `400` naming the rejected keys; malformed values for usable fields return `422`. Custom-field filters apply only to listings, not search.",
             "schema": {
               "type": "object",
               "properties": {
@@ -69548,8 +70093,14 @@
                   "type": "string",
                   "format": "date-time",
                   "description": "ISO 8601 formatted date. Lists only users that were created on and before this datetime"
+                },
+                "customFields": {
+                  "type": "object",
+                  "additionalProperties": true,
+                  "description": "Filter a resource listing by administrator-defined custom fields using literal dotted keys such as `filter[customFields.reference]=INV-42`, not nested `filter[customFields][reference]` keys. Text, email and URL fields accept a single string and use case- and accent-insensitive substring matching; `%`, `_` and backslashes are matched literally. Boolean fields accept `true`, `false`, `1` or `0` as strings, or boolean and integer equivalents. Number, date and date-time fields accept inclusive `filter[customFields.<identifier>][from]` and/or `filter[customFields.<identifier>][to]` bounds, including one-sided ranges. Number bounds are decimal strings from `-99999999999999.999999` to `99999999999999.999999` with at most six fractional places, compared without rounding. Dates use `YYYY-MM-DD` calendar dates; date-times use ISO 8601, with offsets normalized to UTC and no offset interpreted as UTC. Long text and JSON fields are not filterable. Custom-field criteria combine with each other and the resource's other filters using AND. Empty criteria have no effect. Malformed values for usable fields return a property-bound `422` validation error. See each listing operation for how it handles unsupported nonempty criteria."
                 }
-              }
+              },
+              "additionalProperties": true
             }
           },
           "page": {
@@ -69587,12 +70138,18 @@
         "200": {
           "description": "Success"
         },
+        "400": {
+          "description": "Bad Request"
+        },
         "401": {
           "description": "Access token is missing or invalid"
         },
         "403": {
           "description": "You do not have permission to perform the action"
         },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
         "429": {
           "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
         }
@@ -71852,6 +72409,7 @@
       "parameters": {
         "query": {
           "filter": {
+            "description": "Filter vehicles by the documented fields. Add each custom-field criterion as a literal `filter[customFields.<identifier>]` key, not a nested `filter[customFields][<identifier>]` object. Boolean, text, email, and URL criteria use scalar values; number, date, and date-time criteria use inclusive `filter[customFields.<identifier>][from]` and `filter[customFields.<identifier>][to]` bounds. Unfilled criteria are ignored. Filled unknown, unavailable, inaccessible, and non-filterable criteria return `400`; malformed values for usable fields return `422`.",
             "schema": {
               "type": "object",
               "properties": {
@@ -71922,6 +72480,14 @@
                   "format": "date-time",
                   "description": "ISO 8601 formatted date. Lists only the vehicles that were last updated on and before this datetime."
                 }
+              },
+              "additionalProperties": true
+            },
+            "example": {
+              "customFields.fleetReference": "Fleet,North",
+              "customFields.annualDistance": {
+                "from": "10000",
+                "to": "20000"
               }
             }
           },
@@ -71942,11 +72508,17 @@
         "200": {
           "description": "Success"
         },
+        "400": {
+          "description": "Bad Request"
+        },
         "401": {
           "description": "Access token is missing or invalid"
         },
         "403": {
           "description": "You do not have permission to perform the action"
+        },
+        "422": {
+          "description": "The request contains invalid criteria, including malformed custom field filter values"
         }
       }
     },
@@ -73435,7 +74007,7 @@
   ],
   "info": {
     "title": "Public API",
-    "version": "3.256.1",
+    "version": "3.257.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": [
@@ -73449,18 +74021,18 @@
       }
     }
   ],
-  "buildTimestamp": "2026-09-30T15:42:19.337Z",
+  "buildTimestamp": "2026-10-02T12:18:29.790Z",
   "stats": {
-    "totalEndpoints": 658,
-    "originalSize": 6198282,
-    "optimizedSize": 1729692,
-    "reductionPercent": 72.09,
-    "buildDuration": 1134,
+    "totalEndpoints": 666,
+    "originalSize": 6403121,
+    "optimizedSize": 1774310,
+    "reductionPercent": 72.29,
+    "buildDuration": 1651,
     "responseSchemas": {
-      "total": 658,
-      "withSchemas": 658,
-      "totalSchemaSize": 3551045,
-      "averageSchemaSize": 5397
+      "total": 666,
+      "withSchemas": 666,
+      "totalSchemaSize": 3687990,
+      "averageSchemaSize": 5538
     }
   }
 }