@ampeco/public-api-mcp 3.258.1 → 3.259.0

package/dist/generated/endpoints.json

@@ -2426,6 +2426,7 @@
       "method": "POST",
       "operationId": "circuitSetSessionPriority",
       "summary": "Circuit / Set Session Priority",
+      "description": "On built-in DLM circuits, a positive priority other than 1 replaces only the session's state-of-charge (SoC) factor; charge point, connector and user priorities still multiply. With otherwise identical factors and neutral SoC, 2 doubles and 0.5 halves the session's share, subject to capacity limits. Values 0 and 1 use SoC-based weighting; setting the priority back to 1 restores it. Changing the priority of an active built-in session immediately recalculates the root circuit's allocation. On DREEV-integrated circuits, the field's different behavior remains unchanged.",
       "tags": [
         "action / circuit"
       ],
@@ -2496,7 +2497,7 @@
                 "shouldPersist": {
                   "type": "boolean",
                   "default": false,
-                  "description": "Specifies whether the configuration template will be enforced each time the charge point boots."
+                  "description": "Specifies whether the configuration template will be enforced each time the charge point boots. When `true`, a different persistent configuration template already assigned to a charge point is replaced by this one."
                 },
                 "resetType": {
                   "type": "string",
@@ -3759,7 +3760,7 @@
       "method": "POST",
       "operationId": "locationCheckBookingAvailability",
       "summary": "Location / Check Booking Availability",
-      "description": "Get a consolidated view of EVSEs availability for a given location and time frame. Returns available time slots for each bookable EVSE at the location.",
+      "description": "Get a consolidated view of EVSEs availability for a given location and time frame. Returns available time slots for bookable EVSEs at the authorized location. The existing commercial-public candidate pool is preserved, including public EVSEs from other operators available through internal roaming. When userId is supplied, caller-visible commercial-private EVSEs are also included if the user's accepted partner invites have access policies granting the inviting partner's own charge points or charge points shared with that partner. The own-charge-point rule and shared-charge-point option are evaluated independently, and grants from accepted invites are combined. Other charging authorization methods do not substitute for these private booking grants. Personal charge points are excluded. Omitting userId or selecting a visible user without private access returns the same public-only availability.",
       "tags": [
         "action / location"
       ],
@@ -3779,6 +3780,10 @@
             "schema": {
               "type": "object",
               "properties": {
+                "userId": {
+                  "type": "integer",
+                  "description": "Optional booking driver's ID. The user must be visible to the requesting admin. Unknown or invisible users are rejected with a validation error. Null is not accepted."
+                },
                 "startAfter": {
                   "type": "string",
                   "format": "date-time",
@@ -9466,7 +9471,7 @@
       "method": "POST",
       "operationId": "bookingRequestCreate",
       "summary": "Booking Request / Create",
-      "description": "Create a new booking request. If you want to find the available slots for a given location use the Actions / Location / Check Booking Availability",
+      "description": "Create a request to create, update or cancel a booking. Create requests retain the existing commercial-public EVSE selection behavior, including the public internal-roaming candidate pool for automatic selection. Commercial-private EVSEs can additionally be booked for users with accepted partner-invite access-policy grants for own or shared charge points. Other charging authorization does not substitute for these grants, and personal charge points are excluded. See the location check booking availability action (`POST /public-api/actions/locations/v2.0/{location}/check-booking-availability`) for the private eligibility policy and available slots. Update requests evaluate access for the resulting booking user: a supplied userId replaces the user for the proposed update, while omission retains the current booking user. See the update request schema for effective selection and access-rejection semantics. A business rejection still creates a booking request and returns HTTP 201 with status \"rejected\" and a human-readable rejectionReason. The stored result is available through the booking request listing and read operations. Malformed input or supplied references that are unknown or invisible to the requesting admin fail validation with HTTP 422 instead; they do not create a booking request.",
       "tags": [
         "resource / booking requests"
       ],
@@ -9501,7 +9506,7 @@
                     },
                     "rejectionReason": {
                       "type": "string",
-                      "description": "Human-readable reason for rejection. Response behavior: Only present when status is \"rejected\". Omitted for \"pending\" and \"approved\" requests."
+                      "description": "Human-readable business rejection reason, persisted with the booking request and returned by its listing and read operations. Access-related rejections use this existing property, not a separate error code. See the create and update request schema descriptions for access-rejection conditions. Response behavior: Only present when status is \"rejected\". Omitted for \"pending\" and \"approved\" requests."
                     },
                     "createdAt": {
                       "type": "string",
@@ -9513,7 +9518,7 @@
                     },
                     "userId": {
                       "type": "integer",
-                      "description": "ID of the user for whom the booking is made"
+                      "description": "ID of the booking user, who must be visible to the requesting admin. This user's accepted partner-invite access-policy grants determine commercial-private booking eligibility; commercial-public selection remains unchanged."
                     },
                     "locationId": {
                       "type": "integer",
@@ -9536,7 +9541,7 @@
                     },
                     "evseId": {
                       "type": "integer",
-                      "description": "Specific EVSE ID to book. Response behavior: Only present when a specific EVSE was requested. Omitted when EVSE selection was based on criteria or left to the system."
+                      "description": "Specific EVSE ID to book. The reference must be visible to the requesting admin and belong to the requested location. A valid commercial-private reference still requires the booking user's private eligibility; lack of that eligibility is a business rejection, not an unknown-reference validation error. Response behavior: Only present when a specific EVSE was requested. Omitted when EVSE selection was based on criteria or left to the system."
                     },
                     "evseCriteria": {
                       "type": "object",
@@ -9664,7 +9669,7 @@
                     "startAt",
                     "endAt"
                   ],
-                  "description": "Base properties for create booking request (shared between input and response)"
+                  "description": "Base properties for create booking requests, shared between input and response. Existing commercial-public selection is unchanged. Commercial-private eligibility additionally requires the booking user's accepted partner-invite access-policy grants for own or shared charge points; other charging authorization cannot replace these grants. Personal charge points are excluded. See the location check booking availability action for the eligibility policy. If no candidate can be selected, the created request is rejected. Its persisted rejectionReason can include booking-enabled EVSEs that are not accessible to the user, separately from EVSEs with booking disabled and other selection failures."
                 },
                 {
                   "type": "object",
@@ -9691,7 +9696,7 @@
                     },
                     "rejectionReason": {
                       "type": "string",
-                      "description": "Human-readable reason for rejection. Response behavior: Only present when status is \"rejected\". Omitted for \"pending\" and \"approved\" requests."
+                      "description": "Human-readable business rejection reason, persisted with the booking request and returned by its listing and read operations. Access-related rejections use this existing property, not a separate error code. See the create and update request schema descriptions for access-rejection conditions. Response behavior: Only present when status is \"rejected\". Omitted for \"pending\" and \"approved\" requests."
                     },
                     "createdAt": {
                       "type": "string",
@@ -9707,7 +9712,7 @@
                     },
                     "userId": {
                       "type": "integer",
-                      "description": "ID of the user for whom the booking is made"
+                      "description": "ID of the proposed booking user, who must be visible to the requesting admin. Access is evaluated for this resulting user; when omitted, the booking's current user is retained and evaluated. A rejected update does not change the booking's user."
                     },
                     "externalId": {
                       "type": "string",
@@ -9736,7 +9741,7 @@
                     "type",
                     "bookingId"
                   ],
-                  "description": "Base properties for update booking request (shared between input and response)"
+                  "description": "Base properties for update booking requests, shared between input and response. Access is evaluated for the resulting booking user and time slot at the booking's location. Omitting userId retains the current user. The supported update input does not carry evseId, evseCriteria or parkingSpaceCriteria from the original create request; original create criteria are not reapplied by this input. When no candidate remains, the request is rejected for lack of user access if a caller-visible, booking-enabled, access-excluded commercial-private EVSE satisfies the effective update selection requirements. This access attribution is independent of occupancy. Other empty selection results retain the time-slot-unavailable rejection. A successful selection takes precedence over these rejection reasons. An access rejection persists the booking request with status \"rejected\" and rejectionReason \"The booking cannot be updated because the user has no access to a bookable EVSE at the location.\" The existing booking's user, held EVSEs, dates, reservation and reservation cycle remain unchanged."
                 },
                 {
                   "type": "object",
@@ -9763,7 +9768,7 @@
                     },
                     "rejectionReason": {
                       "type": "string",
-                      "description": "Human-readable reason for rejection. Response behavior: Only present when status is \"rejected\". Omitted for \"pending\" and \"approved\" requests."
+                      "description": "Human-readable business rejection reason, persisted with the booking request and returned by its listing and read operations. Access-related rejections use this existing property, not a separate error code. See the create and update request schema descriptions for access-rejection conditions. Response behavior: Only present when status is \"rejected\". Omitted for \"pending\" and \"approved\" requests."
                     },
                     "createdAt": {
                       "type": "string",
@@ -31790,6 +31795,12 @@
             "schema": {
               "type": "object",
               "properties": {
+                "averagePrice": {
+                  "type": "number",
+                  "minimum": 0,
+                  "maximum": 10000000000000,
+                  "description": "Average charging price in the location operator's currency. Submitted prices must be non-negative and use the effective operator currency's unit-price precision. Zero indicates free charging. Omit the property to create a location without an average price."
+                },
                 "id": {
                   "type": "integer"
                 },
@@ -32793,6 +32804,13 @@
             "schema": {
               "type": "object",
               "properties": {
+                "averagePrice": {
+                  "type": "number",
+                  "minimum": 0,
+                  "maximum": 10000000000000,
+                  "nullable": true,
+                  "description": "Average charging price in the location operator's currency. Submitted prices must be non-negative and use the effective operator currency's unit-price precision. Zero indicates free charging. Send null to clear the price; omit the property to preserve the stored price."
+                },
                 "id": {
                   "type": "integer"
                 },
@@ -34305,6 +34323,7 @@
                     "previous_session_not_paid",
                     "unpaid_subscription_fees",
                     "payment_method_required",
+                    "corporate_billing_disabled",
                     "corporate_billing_policy_inactive",
                     "corporate_billing_limit_exceeded",
                     "corporate_account_limit_reached",
@@ -34352,7 +34371,7 @@
                     "ocpi_roaming_not_setup",
                     "command_expired"
                   ],
-                  "description": "The reason a command did not succeed: Authorization and access: - **charging_not_allowed**: Charging is not allowed for the authorizing token - **location_is_closed**: The location was closed when the command was received - **access_restricted**: Access to the charge point is restricted for the authorizing token - **user_verification_not_complete**: The user behind the token has not completed verification - **terms_not_accepted**: The user has not accepted the required terms and policies - **user_is_disabled**: The user account is disabled - **authorization_failed**: The authorization of the token was refused - **pre_authorization_failed**: The payment pre-authorization for the session failed - **token_not_authorized_for_booking**: The token is not authorized to book the requested EVSE - **operator_in_migration_mode**: The operator is in migration mode and does not accept new charging Payment, subscription and billing: - **subscription_required**: A subscription plan is required to start charging - **unpaid_subscription_fees**: The user has unpaid subscription fees - **previous_session_not_paid**: An earlier session of the user is still unpaid - **payment_method_required**: The user has no payment method that can be charged - **payment_method_expired**: The user's payment method has expired - **payment_method_not_allowed**: The user's payment method is not allowed for this charge point - **payment_method_doesnt_have_sufficient_funds**: The user's payment method has insufficient funds - **cannot_bill_payment_method**: The user's payment method could not be billed - **invalid_payment_method_for_direct_charges**: The user's payment method cannot be used for direct charges - **user_invoice_details_not_provided**: The user has not provided the invoice details required to be billed Corporate billing: - **corporate_billing_policy_inactive**: The corporate billing policy is not active - **corporate_billing_limit_exceeded**: The corporate billing policy limit is exceeded - **corporate_account_limit_reached**: The corporate account limit is reached - **corporate_billing_currency_mismatch**: The session currency differs from the corporate billing currency - **corporate_billing_cross_operator_not_opted_in**: The operator serving the session is not opted in to the partner's cross-operator corporate billing - **corporate_billing_exchange_rate_unavailable**: No exchange rate is available to convert the session amount into the corporate billing currency - **corporate_billing_charger_type_not_covered**: The charger type is not covered by the corporate billing policy - **corporate_billing_partner_not_covered**: The partner is not covered by the corporate billing policy - **corporate_billing_country_not_covered**: The country is not covered by the corporate billing policy - **corporate_billing_location_not_covered**: The location is not covered by the corporate billing policy - **corporate_billing_location_tag_not_covered**: The location tag is not covered by the corporate billing policy - **corporate_billing_roaming_not_covered**: Roaming is not covered by the corporate billing policy Tariffs: - **tariff_charging_not_allowed**: The applicable tariff does not allow charging - **no_tariff_group_configured**: No tariff group is configured for the charge point - **tariff_resolution_failed**: No tariff could be resolved for the requested charging Charge point and EVSE state: - **evse_disabled**: The requested EVSE is disabled - **evse_out_of_order**: The requested EVSE is out of order - **evse_occupied**: The requested EVSE is already in use - **evse_inoperative**: The requested EVSE is not operational - **evse_has_queued_reservations**: The requested EVSE has queued reservations - **ev_not_connected_to_evse**: No vehicle is connected to the requested EVSE - **session_already_running**: A charging session is already running RFID tokens: - **rfid_tag_expired**: The RFID tag has expired - **rfid_tag_disabled**: The RFID tag is disabled - **rfid_tag_suspended**: The RFID tag is suspended - **rfid_charge_point_scope_mismatch**: The RFID tag may not be used on the requested charge point Roaming setup: - **ocpi_roaming_not_setup**: The OCPI roaming configuration needed to serve the command is missing - **internal_roaming_not_setup**: The internal roaming configuration needed to serve the command is missing Command execution: - **remote_start_failed**: The charge point refused or failed the remote start - **rejected**: The charge point rejected the command - **failed**: The command failed while it was being executed - **not_supported**: The command is not supported for the requested charge point - **timeout**: The charge point did not respond within the command timeout - **command_expired**: The command was no longer valid by the time it could be executed - **unknown_session**: The referenced charging session is unknown to the platform - **unknown_reservation**: The referenced reservation is unknown to the platform - **canceled_reservation**: The reservation was cancelled instead of being honoured"
+                  "description": "The reason a command did not succeed: Authorization and access: - **charging_not_allowed**: Charging is not allowed for the authorizing token - **location_is_closed**: The location was closed when the command was received - **access_restricted**: Access to the charge point is restricted for the authorizing token - **user_verification_not_complete**: The user behind the token has not completed verification - **terms_not_accepted**: The user has not accepted the required terms and policies - **user_is_disabled**: The user account is disabled - **authorization_failed**: The authorization of the token was refused - **pre_authorization_failed**: The payment pre-authorization for the session failed - **token_not_authorized_for_booking**: The token is not authorized to book the requested EVSE - **operator_in_migration_mode**: The operator is in migration mode and does not accept new charging Payment, subscription and billing: - **subscription_required**: A subscription plan is required to start charging - **unpaid_subscription_fees**: The user has unpaid subscription fees - **previous_session_not_paid**: An earlier session of the user is still unpaid - **payment_method_required**: The user has no payment method that can be charged - **payment_method_expired**: The user's payment method has expired - **payment_method_not_allowed**: The user's payment method is not allowed for this charge point - **payment_method_doesnt_have_sufficient_funds**: The user's payment method has insufficient funds - **cannot_bill_payment_method**: The user's payment method could not be billed - **invalid_payment_method_for_direct_charges**: The user's payment method cannot be used for direct charges - **user_invoice_details_not_provided**: The user has not provided the invoice details required to be billed Corporate billing: - **corporate_billing_disabled**: Corporate billing is switched off for the partner or the driver's accepted invite - **corporate_billing_policy_inactive**: The corporate billing policy is not active - **corporate_billing_limit_exceeded**: The corporate billing policy limit is exceeded - **corporate_account_limit_reached**: Legacy corporate-account refusal value retained for historical records; newly detected disabled billing uses corporate_billing_disabled - **corporate_billing_currency_mismatch**: The session currency differs from the corporate billing currency - **corporate_billing_cross_operator_not_opted_in**: The operator serving the session is not opted in to the partner's cross-operator corporate billing - **corporate_billing_exchange_rate_unavailable**: No exchange rate is available to convert the session amount into the corporate billing currency - **corporate_billing_charger_type_not_covered**: The charger type is not covered by the corporate billing policy - **corporate_billing_partner_not_covered**: The partner is not covered by the corporate billing policy - **corporate_billing_country_not_covered**: The country is not covered by the corporate billing policy - **corporate_billing_location_not_covered**: The location is not covered by the corporate billing policy - **corporate_billing_location_tag_not_covered**: The location tag is not covered by the corporate billing policy - **corporate_billing_roaming_not_covered**: Roaming is not covered by the corporate billing policy Tariffs: - **tariff_charging_not_allowed**: The applicable tariff does not allow charging - **no_tariff_group_configured**: No tariff group is configured for the charge point - **tariff_resolution_failed**: No tariff could be resolved for the requested charging Charge point and EVSE state: - **evse_disabled**: The requested EVSE is disabled - **evse_out_of_order**: The requested EVSE is out of order - **evse_occupied**: The requested EVSE is already in use - **evse_inoperative**: The requested EVSE is not operational - **evse_has_queued_reservations**: The requested EVSE has queued reservations - **ev_not_connected_to_evse**: No vehicle is connected to the requested EVSE - **session_already_running**: A charging session is already running RFID tokens: - **rfid_tag_expired**: The RFID tag has expired - **rfid_tag_disabled**: The RFID tag is disabled - **rfid_tag_suspended**: The RFID tag is suspended - **rfid_charge_point_scope_mismatch**: The RFID tag may not be used on the requested charge point Roaming setup: - **ocpi_roaming_not_setup**: The OCPI roaming configuration needed to serve the command is missing - **internal_roaming_not_setup**: The internal roaming configuration needed to serve the command is missing Command execution: - **remote_start_failed**: The charge point refused or failed the remote start - **rejected**: The charge point rejected the command - **failed**: The command failed while it was being executed - **not_supported**: The command is not supported for the requested charge point - **timeout**: The charge point did not respond within the command timeout - **command_expired**: The command was no longer valid by the time it could be executed - **unknown_session**: The referenced charging session is unknown to the platform - **unknown_reservation**: The referenced reservation is unknown to the platform - **canceled_reservation**: The reservation was cancelled instead of being honoured"
                 },
                 "createdAfter": {
                   "type": "string",
@@ -35953,9 +35972,6 @@
                 "title": {
                   "type": "string"
                 },
-                "partnerId": {
-                  "type": "integer"
-                },
                 "contractType": {
                   "type": "string",
                   "enum": [
@@ -36017,9 +36033,19 @@
                     }
                   }
                 },
+                "partnerId": {
+                  "type": "integer"
+                },
                 "revenueSharing": {
                   "type": "object",
                   "properties": {
+                    "partnerSharePercentagePrivateEvseAccessFees": {
+                      "type": "number",
+                      "format": "float",
+                      "minimum": 0,
+                      "maximum": 100,
+                      "description": "The partner's share of the revenue from private EVSE access fees from other partners given access to this partner's commercial private charge points. Omit the property to leave the share unconfigured."
+                    },
                     "partnerSharePercentageAcEvse": {
                       "type": "number",
                       "format": "float",
@@ -36083,6 +36109,12 @@
                 "monthlyPlatformFees": {
                   "type": "object",
                   "properties": {
+                    "perPrivateEvseOfOtherPartners": {
+                      "type": "number",
+                      "format": "float",
+                      "minimum": 0,
+                      "description": "Fee per EVSE, without tax, of commercial private charge points of other partners to which this partner is given access. Omit the property to leave the fee unconfigured."
+                    },
                     "perChargePoint": {
                       "type": "number",
                       "format": "float",
@@ -36208,9 +36240,6 @@
                 "title": {
                   "type": "string"
                 },
-                "partnerId": {
-                  "type": "integer"
-                },
                 "contractType": {
                   "type": "string",
                   "enum": [
@@ -36272,9 +36301,19 @@
                     }
                   }
                 },
+                "partnerId": {
+                  "type": "integer"
+                },
                 "revenueSharing": {
                   "type": "object",
                   "properties": {
+                    "partnerSharePercentagePrivateEvseAccessFees": {
+                      "type": "number",
+                      "format": "float",
+                      "minimum": 0,
+                      "maximum": 100,
+                      "description": "The partner's share of the revenue from private EVSE access fees from other partners given access to this partner's commercial private charge points. Omit the property to leave the share unconfigured."
+                    },
                     "partnerSharePercentageAcEvse": {
                       "type": "number",
                       "format": "float",
@@ -36338,6 +36377,12 @@
                 "monthlyPlatformFees": {
                   "type": "object",
                   "properties": {
+                    "perPrivateEvseOfOtherPartners": {
+                      "type": "number",
+                      "format": "float",
+                      "minimum": 0,
+                      "description": "Fee per EVSE, without tax, of commercial private charge points of other partners to which this partner is given access. Omit the property to leave the fee unconfigured."
+                    },
                     "perChargePoint": {
                       "type": "number",
                       "format": "float",
@@ -36507,6 +36552,13 @@
                 "revenueSharing": {
                   "type": "object",
                   "properties": {
+                    "partnerSharePercentagePrivateEvseAccessFees": {
+                      "type": "number",
+                      "format": "float",
+                      "minimum": 0,
+                      "maximum": 100,
+                      "description": "The partner's share of the revenue from private EVSE access fees from other partners given access to this partner's commercial private charge points. Omit the property to leave the share unconfigured."
+                    },
                     "partnerSharePercentageAcEvse": {
                       "type": "number",
                       "format": "float",
@@ -36570,6 +36622,12 @@
                 "monthlyPlatformFees": {
                   "type": "object",
                   "properties": {
+                    "perPrivateEvseOfOtherPartners": {
+                      "type": "number",
+                      "format": "float",
+                      "minimum": 0,
+                      "description": "Fee per EVSE, without tax, of commercial private charge points of other partners to which this partner is given access. Omit the property to leave the fee unconfigured."
+                    },
                     "perChargePoint": {
                       "type": "number",
                       "format": "float",
@@ -41067,7 +41125,8 @@
       "method": "GET",
       "operationId": "partnerSettlementReportsListing",
       "summary": "Partner Settlement Reports / Listing",
-      "description": "Get all Partner Settlement Reports",
+      "description": "**This endpoint is deprecated. Use the v1.1 equivalent instead.** Get all Partner Settlement Reports",
+      "deprecated": true,
       "tags": [
         "resource / partner settlement reports"
       ],
@@ -41141,7 +41200,8 @@
       "method": "GET",
       "operationId": "partnerSettlementReportRead",
       "summary": "Partner Settlement Report / Read",
-      "description": "Get a single Partner Settlement Report",
+      "description": "**This endpoint is deprecated. Use the v1.1 equivalent instead.** Get a single Partner Settlement Report",
+      "deprecated": true,
       "tags": [
         "resource / partner settlement reports"
       ],
@@ -41176,7 +41236,8 @@
       "method": "GET",
       "operationId": "partnerSettlementReportPartnerSettlementRecordsListing",
       "summary": "Partner Settlement Report / Partner Settlement Records / Listing",
-      "description": "Get all Partner Settlement Records",
+      "description": "**This endpoint is deprecated. Use the v1.1 equivalent instead.** Get all Partner Settlement Records",
+      "deprecated": true,
       "tags": [
         "resource / partner settlement reports"
       ],
@@ -41224,7 +41285,8 @@
       "method": "POST",
       "operationId": "partnerSettlementReportPartnerSettlementRecordCreate",
       "summary": "Partner Settlement Report / Partner Settlement Record / Create",
-      "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.",
+      "description": "**This endpoint is deprecated. Use the v1.1 equivalent instead.** 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.",
+      "deprecated": true,
       "tags": [
         "resource / partner settlement reports"
       ],
@@ -41295,7 +41357,8 @@
       "method": "GET",
       "operationId": "partnertSettlementReportPartnerSettlementRecordRead",
       "summary": "Partner Settlement Report / Partner Settlement Record / Read",
-      "description": "Read Partner Settlement Record",
+      "description": "**This endpoint is deprecated. Use the v1.1 equivalent instead.** Read Partner Settlement Record",
+      "deprecated": true,
       "tags": [
         "resource / partner settlement reports"
       ],
@@ -41334,7 +41397,8 @@
       "method": "PUT",
       "operationId": "partnerSettlementReportPartnerSettlementRecordUpdate",
       "summary": "Partner Settlement Report / Partner Settlement Record / Update",
-      "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`.",
+      "description": "**This endpoint is deprecated. Use the v1.1 equivalent instead.** 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`.",
+      "deprecated": true,
       "tags": [
         "resource / partner settlement reports"
       ],
@@ -41409,7 +41473,8 @@
       "method": "DELETE",
       "operationId": "partnerSettlementReportPartnerSettlementRecordDelete",
       "summary": "Partner Settlement Report / Partner Settlement Record / Delete",
-      "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.",
+      "description": "**This endpoint is deprecated. Use the v1.1 equivalent instead.** 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.",
+      "deprecated": true,
       "tags": [
         "resource / partner settlement reports"
       ],
@@ -41449,6 +41514,390 @@
         }
       }
     },
+    {
+      "path": "/public-api/resources/partner-settlement-reports/v1.1",
+      "method": "GET",
+      "operationId": "partnerSettlementReportsListingV1_1",
+      "summary": "Partner Settlement Reports / Listing",
+      "description": "Get all Partner Settlement Reports",
+      "tags": [
+        "resource / partner settlement reports"
+      ],
+      "parameters": {
+        "query": {
+          "filter": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "partnerId": {
+                  "type": "integer"
+                },
+                "periodAfter": {
+                  "type": "string",
+                  "format": "date"
+                },
+                "periodBefore": {
+                  "type": "string",
+                  "format": "date"
+                },
+                "customFields": {
+                  "type": "string",
+                  "example": "filter[customFields.invoiceReference]=INV-42",
+                  "description": "Filter a custom-field host resource by custom fields defined for that resource. Add one literal `customFields.<identifier>` key to the existing `filter` object for each criterion. The identifier suffix is administrator-defined and is never enumerated in this schema or generated per tenant. Use a scalar for boolean, text, email, and URL fields. Boolean accepts booleans and integer `1` or `0`, as well as the strings `\"true\"`, `\"false\"`, `\"1\"`, and `\"0\"`. Text, email, and URL accept strings and use contains matching that is case- and accent-insensitive; backslashes, `%`, and `_` are treated literally rather than as pattern syntax. Use `from`, `to`, or both below the dotted key for number, date, and date-time fields. Both bounds are inclusive. Number bounds are decimal strings from `-99999999999999.999999` through `99999999999999.999999` with at most six decimal places; comparisons preserve submitted and stored decimal precision without rounding. Date bounds use `YYYY-MM-DD` and compare calendar dates without time-zone conversion. Date-time bounds use ISO 8601; offsets are normalized to UTC, and an omitted offset is interpreted as UTC. Multiple identifiers combine with AND. Empty scalar criteria and ranges whose bounds are empty are ignored. An identifier resolves only to its current active definition, so values belonging to a deleted definition never match if its identifier is reused. Operator-scoped filters match only host records whose current operator owner is assigned to the field; retained inapplicable values are excluded before pagination. Criteria the request cannot use return `400` and name the rejected keys, and no criterion in the request is applied. This covers unknown, inaccessible, disabled, and deleted identifiers, and fields whose filtering is disabled or whose type does not support filtering. For a usable field, malformed objects or values, a criterion shape that is invalid for the field type, and a range whose `from` bound is greater than its `to` bound return `422`. Custom-field filters apply only to resource listings. They do not participate in search and do not depend on an `include` parameter; any unrelated includes are defined by the host resource. Examples: `filter[customFields.invoiceReference]=INV-42` and `filter[customFields.capacity][from]=10&filter[customFields.capacity][to]=20`. URL-encode the query keys and values when sending the request."
+                },
+                "externalId": {
+                  "type": "string"
+                }
+              }
+            }
+          },
+          "per_page": {
+            "description": "The number of items to return per page.",
+            "type": "integer",
+            "minimum": 1,
+            "maximum": 100,
+            "default": 100
+          },
+          "cursor": {
+            "description": "The cursor to fetch the next page. **Do not construct this value manually.** Use one of the following methods: - Use the value from the previous response's `links.next` to fetch the next page - Pass an empty string (e.g., `?cursor` or `?cursor=`) to initiate cursor pagination on the first page",
+            "type": "string"
+          }
+        }
+      },
+      "responses": {
+        "200": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport}",
+      "method": "GET",
+      "operationId": "partnerSettlementReportReadV1_1",
+      "summary": "Partner Settlement Report / Read",
+      "description": "Get a single Partner Settlement Report",
+      "tags": [
+        "resource / partner settlement reports"
+      ],
+      "parameters": {
+        "path": {
+          "partnerSettlementReport": {
+            "type": "integer",
+            "required": true
+          }
+        }
+      },
+      "responses": {
+        "200": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport}/records",
+      "method": "GET",
+      "operationId": "partnerSettlementReportPartnerSettlementRecordsListingV1_1",
+      "summary": "Partner Settlement Report / Partner Settlement Records / Listing",
+      "description": "Get all Partner Settlement Records",
+      "tags": [
+        "resource / partner settlement reports"
+      ],
+      "parameters": {
+        "path": {
+          "partnerSettlementReport": {
+            "type": "integer",
+            "required": true
+          }
+        },
+        "query": {
+          "per_page": {
+            "description": "The number of items to return per page.",
+            "type": "integer",
+            "minimum": 1,
+            "maximum": 100,
+            "default": 100
+          },
+          "cursor": {
+            "description": "The cursor to fetch the next page. **Do not construct this value manually.** Use one of the following methods: - Use the value from the previous response's `links.next` to fetch the next page - Pass an empty string (e.g., `?cursor` or `?cursor=`) to initiate cursor pagination on the first page",
+            "type": "string"
+          }
+        }
+      },
+      "responses": {
+        "200": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport}/records",
+      "method": "POST",
+      "operationId": "partnerSettlementReportPartnerSettlementRecordCreateV1_1",
+      "summary": "Partner Settlement Report / Partner Settlement Record / Create",
+      "description": "Create Partner Settlement Record",
+      "tags": [
+        "resource / partner settlement reports"
+      ],
+      "parameters": {
+        "path": {
+          "partnerSettlementReport": {
+            "type": "integer",
+            "required": true
+          }
+        }
+      },
+      "requestBody": {
+        "required": true,
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "date": {
+                  "type": "string",
+                  "format": "date",
+                  "description": "Date the payment was made."
+                },
+                "paidAmount": {
+                  "type": "number",
+                  "description": "Amount recorded as paid, in the settlement report's currency. Negative values record a reversing entry."
+                },
+                "note": {
+                  "type": "string",
+                  "description": "Free-text note on the settlement record."
+                }
+              },
+              "required": [
+                "date",
+                "paidAmount",
+                "note"
+              ]
+            }
+          }
+        }
+      },
+      "responses": {
+        "201": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "409": {
+          "description": "The 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"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport}/records/{partnerSettlementRecord}",
+      "method": "GET",
+      "operationId": "partnerSettlementReportPartnerSettlementRecordReadV1_1",
+      "summary": "Partner Settlement Report / Partner Settlement Record / Read",
+      "description": "Read Partner Settlement Record",
+      "tags": [
+        "resource / partner settlement reports"
+      ],
+      "parameters": {
+        "path": {
+          "partnerSettlementReport": {
+            "type": "integer",
+            "required": true
+          },
+          "partnerSettlementRecord": {
+            "type": "integer",
+            "required": true
+          }
+        }
+      },
+      "responses": {
+        "200": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport}/records/{partnerSettlementRecord}",
+      "method": "PUT",
+      "operationId": "partnerSettlementReportPartnerSettlementRecordUpdateV1_1",
+      "summary": "Partner Settlement Report / Partner Settlement Record / Update",
+      "description": "Update a single Partner Settlement Record",
+      "tags": [
+        "resource / partner settlement reports"
+      ],
+      "parameters": {
+        "path": {
+          "partnerSettlementReport": {
+            "type": "integer",
+            "required": true
+          },
+          "partnerSettlementRecord": {
+            "type": "integer",
+            "required": true
+          }
+        }
+      },
+      "requestBody": {
+        "required": true,
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "date": {
+                  "type": "string",
+                  "format": "date",
+                  "description": "Date the payment was made."
+                },
+                "paidAmount": {
+                  "type": "number",
+                  "description": "Amount recorded as paid, in the settlement report's currency. Negative values record a reversing entry."
+                },
+                "note": {
+                  "type": "string",
+                  "description": "Free-text note on the settlement record."
+                }
+              },
+              "required": [
+                "date",
+                "paidAmount",
+                "note"
+              ]
+            }
+          }
+        }
+      },
+      "responses": {
+        "200": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "409": {
+          "description": "The 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"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
+    {
+      "path": "/public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport}/records/{partnerSettlementRecord}",
+      "method": "DELETE",
+      "operationId": "partnerSettlementReportPartnerSettlementRecordDeleteV1_1",
+      "summary": "Partner Settlement Report / Partner Settlement Record / Delete",
+      "description": "Delete a single Partner Settlement Record",
+      "tags": [
+        "resource / partner settlement reports"
+      ],
+      "parameters": {
+        "path": {
+          "partnerSettlementReport": {
+            "type": "integer",
+            "required": true
+          },
+          "partnerSettlementRecord": {
+            "type": "integer",
+            "required": true
+          }
+        }
+      },
+      "responses": {
+        "204": {
+          "description": "Success"
+        },
+        "401": {
+          "description": "Access token is missing or invalid"
+        },
+        "403": {
+          "description": "You do not have permission to perform the action"
+        },
+        "404": {
+          "description": "The record is not found"
+        },
+        "409": {
+          "description": "The 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"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
     {
       "path": "/public-api/resources/partners/v1.0",
       "method": "GET",
@@ -54800,7 +55249,7 @@
             "default": false
           },
           "include": {
-            "description": "Include additional information in the response. The following options are available:<br> - `externalAppData`: Include external application data in the response<br> - `chargingProfile`: Include the TX charging profile applied to the session in the response<br> - `vehicle`: Include the nested `vehicle` object describing the vehicle associated with the session<br> - `timelineSnapshot`: Include the pre-computed timeline snapshot for a finished session when available",
+            "description": "Include additional information in the response. The following options are available:<br> - `externalAppData`: Include external application data in the response<br> - `chargingProfile`: Include the TX charging profile applied to the session in the response<br> - `vehicle`: Include the nested `vehicle` object describing the vehicle associated with the session<br> - `timelineSnapshot`: Include the pre-computed timeline snapshot for a finished session when available<br> - `reimbursementRecords`: Include the reimbursement records of the session, when the caller may view reimbursement records",
             "schema": {
               "type": "array",
               "items": {
@@ -54809,7 +55258,8 @@
                   "externalAppData",
                   "chargingProfile",
                   "vehicle",
-                  "timelineSnapshot"
+                  "timelineSnapshot",
+                  "reimbursementRecords"
                 ]
               }
             }
@@ -74884,7 +75334,7 @@
   ],
   "info": {
     "title": "Public API",
-    "version": "3.258.1",
+    "version": "3.259.0",
     "description": "The Public API provides server-to-server integration capabilities for your EV charging platform.\n\n**Authentication.** Existing integrations continue to work unchanged — long-lived UUID admin tokens are sent in `Authorization: Bearer ...` with no exchange required. Two security schemes are documented for OpenAPI client tooling, both resulting in the same Bearer header at the wire level:\n   - `bearerAuth` — the token in the `Authorization: Bearer ...` header is either a long-lived UUID admin token (issued via the admin UI, used directly) or a short-lived access token previously obtained via OAuth.\n   - `oauth2ClientCredentials` - a `client_id` / `client_secret` pair should be exchanged for a short-lived access token at `/public-api/oauth/token` per RFC 6749 Section 4.4 (Client Credentials Grant), and the short-lived token should be used in the `Authorization: Bearer ...` header. The OAuth `client_secret` itself cannot be sent directly as a bearer token — it must be exchanged first.\n"
   },
   "servers": [
@@ -74898,18 +75348,18 @@
       }
     }
   ],
-  "buildTimestamp": "2026-10-06T10:24:39.658Z",
+  "buildTimestamp": "2026-10-06T10:47:25.976Z",
   "stats": {
-    "totalEndpoints": 679,
-    "originalSize": 6525064,
-    "optimizedSize": 1829203,
-    "reductionPercent": 71.97,
-    "buildDuration": 1695,
+    "totalEndpoints": 686,
+    "originalSize": 6612313,
+    "optimizedSize": 1849798,
+    "reductionPercent": 72.02,
+    "buildDuration": 1462,
     "responseSchemas": {
-      "total": 679,
-      "withSchemas": 679,
-      "totalSchemaSize": 3739771,
-      "averageSchemaSize": 5508
+      "total": 686,
+      "withSchemas": 686,
+      "totalSchemaSize": 3802765,
+      "averageSchemaSize": 5543
     }
   }
 }