@ampeco/public-api-mcp 3.246.0 → 3.247.1

package/dist/generated/build-stats.json

@@ -1,13 +1,13 @@
 {
   "totalEndpoints": 640,
-  "originalSize": 5825490,
-  "optimizedSize": 1630992,
-  "reductionPercent": 72,
-  "buildDuration": 1752,
+  "originalSize": 5828593,
+  "optimizedSize": 1631472,
+  "reductionPercent": 72.01,
+  "buildDuration": 1090,
   "responseSchemas": {
     "total": 640,
     "withSchemas": 640,
-    "totalSchemaSize": 3315541,
-    "averageSchemaSize": 5181
+    "totalSchemaSize": 3317461,
+    "averageSchemaSize": 5184
   }
 }

package/dist/generated/endpoints.json

@@ -48645,9 +48645,10 @@
                   "type": "string",
                   "enum": [
                     "policy",
-                    "charge_point"
+                    "charge_point",
+                    "integration"
                   ],
-                  "description": "Origin of the per-kWh rate used to reimburse a home-charging session: - **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy. - **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy."
+                  "description": "Origin of the per-kWh rate used to reimburse a home-charging session: - **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy. - **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy. - **integration**: An integration resolves the electricity rate — for example by the charge point's region. The integration and its region-to-rate bindings are configured in the admin panel. `electricityRateId` is not set on the policy."
                 }
               }
             }
@@ -48695,14 +48696,6 @@
                   "type": "string",
                   "maxLength": 255
                 },
-                "electricityRateSource": {
-                  "type": "string",
-                  "enum": [
-                    "policy",
-                    "charge_point"
-                  ],
-                  "description": "Origin of the per-kWh rate used to reimburse a home-charging session: - **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy. - **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy."
-                },
                 "validityStartsOn": {
                   "type": "string",
                   "format": "date",
@@ -48725,6 +48718,14 @@
                   "format": "date",
                   "description": "Uses the YYYY-MM-DD date format."
                 },
+                "electricityRateSource": {
+                  "type": "string",
+                  "enum": [
+                    "policy",
+                    "charge_point"
+                  ],
+                  "description": "Origin of the per-kWh rate used to reimburse a home-charging session: - **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy. - **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy. The `integration` source is not writable through this API: it cannot be submitted on create or update. Policies using it are configured in the admin panel."
+                },
                 "operatorId": {
                   "type": "integer",
                   "example": 1,
@@ -48791,7 +48792,7 @@
       "method": "DELETE",
       "operationId": "reimbursementPolicyDelete",
       "summary": "Reimbursement policy / Delete",
-      "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. Delete a reimbursement policy. Deletion is rejected while the policy is attached to partner invites.",
+      "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. Delete a reimbursement policy. Deletion is rejected only while the policy is attached to partner invites. A policy is deletable whatever its `electricityRateSource` is, `integration` included; the restrictions on submitting `electricityRateSource` are described on the create and update operations and do not apply here.",
       "tags": [
         "resource / reimbursement policies"
       ],
@@ -48824,7 +48825,7 @@
       "method": "PATCH",
       "operationId": "reimbursementPolicyUpdate",
       "summary": "Reimbursement policy / Update",
-      "description": "⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. Update a reimbursement policy. The update is rejected with 409 while the requested change conflicts with the rate the policy resolves — selecting the `charge_point` rate source while an attached charge point has no electricity rate. That conflict clears only when the configuration changes: give the charge point a rate, or detach it from the policy. Every other rejection of the request body is reported as 422, keyed by the offending field — malformed or invalid field values, and changing `partnerId` on a policy that is already assigned to partner invites or has active charge point attachments, which returns a `partnerId` validation error rather than a 409. Deactivated attachments do not block the change.",
+      "description": "⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed. Update a reimbursement policy. The update is rejected with 409 while the requested change conflicts with the rate the policy resolves — selecting the `charge_point` rate source while an attached charge point has no electricity rate. That conflict clears only when the configuration changes: give the charge point a rate, or detach it from the policy. A policy whose stored `electricityRateSource` is `integration` is updated through this API like any other policy, except that its rate source cannot be changed: a request that submits `electricityRateSource` on such a policy is rejected with 409, because the integration that resolves its rate is configured in the admin panel and the binding could not be restored through this API. Omit `electricityRateSource` to update `name`, the validity dates or the partner scope. Every other rejection of the request body is reported as 422, keyed by the offending field — malformed or invalid field values, and changing `partnerId` on a policy that is already assigned to partner invites or has active charge point attachments, which returns a `partnerId` validation error rather than a 409. Deactivated attachments do not block the change.",
       "tags": [
         "resource / reimbursement policies"
       ],
@@ -48839,18 +48840,18 @@
                   "type": "string",
                   "maxLength": 255
                 },
+                "validityStartsOn": {
+                  "type": "string",
+                  "format": "date",
+                  "description": "Uses the YYYY-MM-DD date format."
+                },
                 "electricityRateSource": {
                   "type": "string",
                   "enum": [
                     "policy",
                     "charge_point"
                   ],
-                  "description": "Origin of the per-kWh rate used to reimburse a home-charging session: - **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy. - **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy."
-                },
-                "validityStartsOn": {
-                  "type": "string",
-                  "format": "date",
-                  "description": "Uses the YYYY-MM-DD date format."
+                  "description": "Origin of the per-kWh rate used to reimburse a home-charging session: - **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy. - **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy. The `integration` source is not writable through this API: it cannot be submitted on create or update. Policies using it are configured in the admin panel."
                 },
                 "partnerId": {
                   "type": "integer",
@@ -67616,7 +67617,7 @@
       "method": "POST",
       "operationId": "paymentMethodCreate",
       "summary": "Payment Method / Create",
-      "description": "Initiate a new payment method registration, or finalize it. Note that this is a two step process! # For payment processors with web view integration You will need to initiate a call with no parameters to this endpoint to get a new request to add payment method (Step 1). Then you will have to redirect to an endpoint and wait for the client to enter his credit card details there. Once he/she is done (and reaches the successURL) you must then issue another call to this endpoint with the transactionID that was returned from the first call to finalize the process and retrieve the newly added payment method data (Step 2). ## Step 1 POST with request body, containing `tokenizedType` to determine the type of the method and `bankTransferType` if applicable. This will create a new request to the payment processor for adding a new payment method. As response you will get the `transactionId` to track the payment method registration process, the `redirectUrl` and `successUrl`, to redirect your user to, along with any other attributes that the payment processor requires for tracking. Just pass those additional parameters to Step 2. ### Example request for tokenizedType = card Request: ```json { \"tokenizedType\": \"card\" } ``` ### Example request for tokenizedType = bank_transfer Request: ```json { \"tokenizedType\": \"bank_transfer\", \"bankTransferType\": \"sepa\" } ``` Response: ```json { \"transactionId\": 1234, \"successUrl\": \"http://example.com/payment-processor/success\", \"redirectUrl\": \"http://example.com/payment-processor/web-form/123abc\", \"additionalProcessorArguments\": \"just pass them all top the step 2\" } ``` ## Step 2 POST with request body, containing the `transactionId` along with any other attributes, that were in the response of Step 1 (other then the `transactionId`, `successUrl` and `redirectUrl`). This will finalize the payment method registration and will retrieve the newly added payment method for you. Note that you can also receive the payment methods using the payment methods listing endpoints. ### Example Request: ```json { \"transactionId\": 1234, \"successUrl\": \"http://example.com/payment-processor/success\", \"redirectUrl\": \"http://example.com/payment-processor/web-form/123abc\", \"additionalProcessorArguments\": \"just pass them all top the step 2\" } ``` Response for card: ```json { \"data\": { \"id\": 1234, \"name\": \"**** 1111\", \"type\": \"tokenized\", \"tokenizedType\": \"card\", \"issuer\": \"visa\", \"cardNetwork\": \"visa\", \"cardType\": \"credit\", \"bin\": \"411111\", \"fingerprint\": \"CjhjhUJ7EaIGzKuYpHGTLLsG6pNs5\", \"acquirerName\": \"Worldline\", \"expireYear\": 2026, \"expireMonth\": 5, \"default\": true, } } ``` Response for bank transfer: ```json { \"data\": { \"id\": 1234, \"name\": \"**** 1111\", \"type\": \"tokenized\", \"tokenizedType\": \"bank_transfer\", \"bankTransferType\": \"sepa\", \"issuer\": null, \"expireYear\": null, \"expireMonth\": null, \"default\": true, } } ``` # For payment processors with in-app integration Braintree and Stripe integrations DO NOT count out `redirectUrl` as these processors should have an ip-app integration and therefore the app itself should use the appropriate SDK to complete the credit-card tokenization process with the processor. ## Braintree The first step is not required for braintree as the full integration is done in-app. Step 2 needs to pass the `paymentMethodNonce` so that it can be exchanged for the payment method token. ### Example Step 2 Request: ```json {\"paymentMethodNonce\": \"abc123\"} ``` Response for card: ```json { \"data\": { \"id\": 1234, \"name\": \"**** 1111\", \"type\": \"tokenized\", \"tokenizedType\": \"card\", \"issuer\": \"visa\", \"cardNetwork\": \"visa\", \"cardType\": \"credit\", \"bin\": \"411111\", \"fingerprint\": \"CjhjhUJ7EaIGzKuYpHGTLLsG6pNs5\", \"acquirerName\": \"Worldline\", \"expireYear\": 2026, \"expireMonth\": 5, \"default\": true, } } ``` Response for bank transfer: ```json { \"data\": { \"id\": 1234, \"name\": \"**** 1111\", \"type\": \"tokenized\", \"tokenizedType\": \"bank_transfer\", \"bankTransferType\": \"sepa\", \"issuer\": null, \"expireYear\": null, \"expireMonth\": null, \"default\": true, } } ``` ## Stripe Step 1 with stripe will initialize a setup intent, that your app should complete. You will get the details you need in order to do that from the response of that call. Call step 2 once you have completed the setup intent. ### Example Step 1 - when tokenizing card ```json { \"tokenizedType\": \"card\" } ``` ### Example Step 1 - when tokenizing bank transfer Request: ```json { \"tokenizedType\": \"bank_transfer\", \"bankTransferType\": \"sepa\" } ``` Response: ```json { \"publishableKey\": \"345678986543\", \"clientSecret\": \"jyt37hgsv63\", \"setupIntentReference\": \"1234ABC\" } ``` ### Example Step 2 Request: ```json { \"publishableKey\": \"345678986543\", \"clientSecret\": \"jyt37hgsv63\", \"setupIntentReference\": \"1234ABC\" } ``` Response for card: ```json { \"data\": { \"id\": 1234, \"name\": \"**** 1111\", \"type\": \"tokenized\", \"tokenizedType\": \"card\", \"issuer\": \"visa\", \"cardNetwork\": \"visa\", \"cardType\": \"credit\", \"bin\": \"411111\", \"fingerprint\": \"CjhjhUJ7EaIGzKuYpHGTLLsG6pNs5\", \"acquirerName\": \"Worldline\", \"expireYear\": 2026, \"expireMonth\": 5, \"default\": true, } } ``` Response for bank transfer: ```json { \"data\": { \"id\": 1234, \"name\": \"**** 1111\", \"type\": \"tokenized\", \"tokenizedType\": \"bank_transfer\", \"bankTransferType\": \"sepa\", \"issuer\": null, \"expireYear\": null, \"expireMonth\": null, \"default\": true, } } ```",
+      "description": "Initiate a new payment method registration, or finalize it. Note that this is a two step process! # For payment processors with web view integration You will need to initiate a call with no parameters to this endpoint to get a new request to add payment method (Step 1). Then you will have to redirect to an endpoint and wait for the client to enter his credit card details there. Once he/she is done (and reaches the successURL) you must then issue another call to this endpoint with the transactionID that was returned from the first call to finalize the process and retrieve the newly added payment method data (Step 2). ## Step 1 POST with request body, containing `tokenizedType` to determine the type of the method and `bankTransferType` if applicable. This will create a new request to the payment processor for adding a new payment method. As response you will get the `transactionId` to track the payment method registration process, the `redirectUrl` and `successUrl`, to redirect your user to, along with any other attributes that the payment processor requires for tracking. Just pass those additional parameters to Step 2. ### Example request for tokenizedType = card Request: ```json { \"tokenizedType\": \"card\" } ``` ### Example request for tokenizedType = bank_transfer Request: ```json { \"tokenizedType\": \"bank_transfer\", \"bankTransferType\": \"sepa\" } ``` Response: ```json { \"transactionId\": 1234, \"successUrl\": \"http://example.com/payment-processor/success\", \"redirectUrl\": \"http://example.com/payment-processor/web-form/123abc\", \"additionalProcessorArguments\": \"just pass them all top the step 2\" } ``` ## Step 2 POST with request body, containing the `transactionId` along with any other attributes, that were in the response of Step 1 (other then the `transactionId`, `successUrl` and `redirectUrl`). This will finalize the payment method registration and will retrieve the newly added payment method for you. Note that you can also receive the payment methods using the payment methods listing endpoints. The finalized payment method is returned in a `data` wrapper. Depending on the payment processor, the status is `200` or `201`; the body is the same in both cases. The optional `token` and `registrationTransactionId` properties are omitted when they are not set rather than returned as `null`; the card example includes both properties, while the bank transfer example omits `registrationTransactionId`. ### Example Request: ```json { \"transactionId\": 1234, \"successUrl\": \"http://example.com/payment-processor/success\", \"redirectUrl\": \"http://example.com/payment-processor/web-form/123abc\", \"additionalProcessorArguments\": \"just pass them all top the step 2\" } ``` Response: see the `Step 2 - card payment method` and `Step 2 - bank transfer payment method` response examples. # For payment processors with in-app integration Braintree and Stripe integrations DO NOT count out `redirectUrl` as these processors should have an ip-app integration and therefore the app itself should use the appropriate SDK to complete the credit-card tokenization process with the processor. ## Braintree The first step is not required for braintree as the full integration is done in-app. Step 2 needs to pass the `paymentMethodNonce` so that it can be exchanged for the payment method token. ### Example Step 2 Request: ```json {\"paymentMethodNonce\": \"abc123\"} ``` Response: see the `Step 2 - card payment method` and `Step 2 - bank transfer payment method` response examples. ## Stripe Step 1 with stripe will initialize a setup intent, that your app should complete. You will get the details you need in order to do that from the response of that call. Call step 2 once you have completed the setup intent. ### Example Step 1 - when tokenizing card ```json { \"tokenizedType\": \"card\" } ``` ### Example Step 1 - when tokenizing bank transfer Request: ```json { \"tokenizedType\": \"bank_transfer\", \"bankTransferType\": \"sepa\" } ``` Response: ```json { \"publishableKey\": \"345678986543\", \"clientSecret\": \"jyt37hgsv63\", \"setupIntentReference\": \"1234ABC\" } ``` ### Example Step 2 Request: ```json { \"publishableKey\": \"345678986543\", \"clientSecret\": \"jyt37hgsv63\", \"setupIntentReference\": \"1234ABC\" } ``` Response: see the `Step 2 - card payment method` and `Step 2 - bank transfer payment method` response examples.",
       "tags": [
         "resource / users"
       ],
@@ -67700,10 +67701,10 @@
       },
       "responses": {
         "200": {
-          "description": "Request succeeded"
+          "description": "Request succeeded. Step 1 returns one of the shapes below. Depending on the payment processor, step 2 may also return `200` with the finalized payment method body documented under the `201` response."
         },
         "201": {
-          "description": "Request succeeded"
+          "description": "The registration created a new payment method. The finalized payment method is returned in a `data` wrapper."
         },
         "401": {
           "description": "Access token is missing or invalid"
@@ -67711,8 +67712,14 @@
         "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 or problem with processing the request has occurred"
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
         }
       }
     },
@@ -71921,7 +71928,7 @@
   ],
   "info": {
     "title": "Public API",
-    "version": "3.246.0",
+    "version": "3.247.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": [
@@ -71935,18 +71942,18 @@
       }
     }
   ],
-  "buildTimestamp": "2026-09-09T11:53:44.781Z",
+  "buildTimestamp": "2026-09-10T16:24:08.274Z",
   "stats": {
     "totalEndpoints": 640,
-    "originalSize": 5825490,
-    "optimizedSize": 1630992,
-    "reductionPercent": 72,
-    "buildDuration": 1752,
+    "originalSize": 5828593,
+    "optimizedSize": 1631472,
+    "reductionPercent": 72.01,
+    "buildDuration": 1090,
     "responseSchemas": {
       "total": 640,
       "withSchemas": 640,
-      "totalSchemaSize": 3315541,
-      "averageSchemaSize": 5181
+      "totalSchemaSize": 3317461,
+      "averageSchemaSize": 5184
     }
   }
 }

package/dist/generated/response-schemas.json

@@ -9849,11 +9849,12 @@
                 "description": "Monetary rate per kWh applied when computing the reimbursement amount, in the record currency. Its origin is given by `electricityRateSource`. Omitted, together with `electricityRateSource`, on records computed before the platform required a resolved rate; such records are no longer produced."
               },
               "electricityRateSource": {
-                "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n",
+                "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n- **integration**: An integration resolves the electricity rate — for example by the charge point's region. The integration and its region-to-rate bindings are configured in the admin panel. `electricityRateId` is not set on the policy.\n",
                 "type": "string",
                 "enum": [
                   "policy",
-                  "charge_point"
+                  "charge_point",
+                  "integration"
                 ]
               },
               "taxBasis": {
@@ -115974,14 +115975,6 @@
                   "type": "string",
                   "maxLength": 255
                 },
-                "electricityRateSource": {
-                  "type": "string",
-                  "enum": [
-                    "policy",
-                    "charge_point"
-                  ],
-                  "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n"
-                },
                 "validityStartsOn": {
                   "description": "Uses the YYYY-MM-DD date format.",
                   "type": "string",
@@ -116004,6 +115997,15 @@
                   "type": "string",
                   "format": "date"
                 },
+                "electricityRateSource": {
+                  "type": "string",
+                  "enum": [
+                    "policy",
+                    "charge_point",
+                    "integration"
+                  ],
+                  "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n- **integration**: An integration resolves the electricity rate — for example by the charge point's region. The integration and its region-to-rate bindings are configured in the admin panel. `electricityRateId` is not set on the policy.\n"
+                },
                 "id": {
                   "type": "integer",
                   "readOnly": true
@@ -116163,14 +116165,6 @@
                 "type": "string",
                 "maxLength": 255
               },
-              "electricityRateSource": {
-                "type": "string",
-                "enum": [
-                  "policy",
-                  "charge_point"
-                ],
-                "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n"
-              },
               "validityStartsOn": {
                 "description": "Uses the YYYY-MM-DD date format.",
                 "type": "string",
@@ -116193,6 +116187,15 @@
                 "type": "string",
                 "format": "date"
               },
+              "electricityRateSource": {
+                "type": "string",
+                "enum": [
+                  "policy",
+                  "charge_point",
+                  "integration"
+                ],
+                "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n- **integration**: An integration resolves the electricity rate — for example by the charge point's region. The integration and its region-to-rate bindings are configured in the admin panel. `electricityRateId` is not set on the policy.\n"
+              },
               "id": {
                 "type": "integer",
                 "readOnly": true
@@ -116293,14 +116296,6 @@
                 "type": "string",
                 "maxLength": 255
               },
-              "electricityRateSource": {
-                "type": "string",
-                "enum": [
-                  "policy",
-                  "charge_point"
-                ],
-                "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n"
-              },
               "validityStartsOn": {
                 "description": "Uses the YYYY-MM-DD date format.",
                 "type": "string",
@@ -116323,6 +116318,15 @@
                 "type": "string",
                 "format": "date"
               },
+              "electricityRateSource": {
+                "type": "string",
+                "enum": [
+                  "policy",
+                  "charge_point",
+                  "integration"
+                ],
+                "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n- **integration**: An integration resolves the electricity rate — for example by the charge point's region. The integration and its region-to-rate bindings are configured in the admin panel. `electricityRateId` is not set on the policy.\n"
+              },
               "id": {
                 "type": "integer",
                 "readOnly": true
@@ -116486,14 +116490,6 @@
                 "type": "string",
                 "maxLength": 255
               },
-              "electricityRateSource": {
-                "type": "string",
-                "enum": [
-                  "policy",
-                  "charge_point"
-                ],
-                "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n"
-              },
               "validityStartsOn": {
                 "description": "Uses the YYYY-MM-DD date format.",
                 "type": "string",
@@ -116516,6 +116512,15 @@
                 "type": "string",
                 "format": "date"
               },
+              "electricityRateSource": {
+                "type": "string",
+                "enum": [
+                  "policy",
+                  "charge_point",
+                  "integration"
+                ],
+                "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n- **integration**: An integration resolves the electricity rate — for example by the charge point's region. The integration and its region-to-rate bindings are configured in the admin panel. `electricityRateId` is not set on the policy.\n"
+              },
               "id": {
                 "type": "integer",
                 "readOnly": true
@@ -116680,11 +116685,12 @@
                   "description": "Monetary rate per kWh applied when computing the reimbursement amount, in the record currency. Its origin is given by `electricityRateSource`. Omitted, together with `electricityRateSource`, on records computed before the platform required a resolved rate; such records are no longer produced."
                 },
                 "electricityRateSource": {
-                  "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n",
+                  "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n- **integration**: An integration resolves the electricity rate — for example by the charge point's region. The integration and its region-to-rate bindings are configured in the admin panel. `electricityRateId` is not set on the policy.\n",
                   "type": "string",
                   "enum": [
                     "policy",
-                    "charge_point"
+                    "charge_point",
+                    "integration"
                   ]
                 },
                 "taxBasis": {
@@ -117144,11 +117150,12 @@
                 "description": "Monetary rate per kWh applied when computing the reimbursement amount, in the record currency. Its origin is given by `electricityRateSource`. Omitted, together with `electricityRateSource`, on records computed before the platform required a resolved rate; such records are no longer produced."
               },
               "electricityRateSource": {
-                "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n",
+                "description": "Origin of the per-kWh rate used to reimburse a home-charging session:\n- **policy**: The electricity rate linked to the policy provides the rate. `electricityRateId` is required and must belong to the same operator as the policy.\n- **charge_point**: The electricity rate assigned to the personal charge point provides the rate, whichever surface assigned it. `electricityRateId` must not be set on the policy.\n- **integration**: An integration resolves the electricity rate — for example by the charge point's region. The integration and its region-to-rate bindings are configured in the admin panel. `electricityRateId` is not set on the policy.\n",
                 "type": "string",
                 "enum": [
                   "policy",
-                  "charge_point"
+                  "charge_point",
+                  "integration"
                 ]
               },
               "taxBasis": {
@@ -169556,6 +169563,16 @@
         }
       }
     },
+    "404": {
+      "schema": {
+        "type": "object",
+        "properties": {
+          "message": {
+            "type": "string"
+          }
+        }
+      }
+    },
     "422": {
       "schema": {
         "type": "object",
@@ -169578,6 +169595,16 @@
           }
         }
       }
+    },
+    "429": {
+      "schema": {
+        "type": "object",
+        "properties": {
+          "message": {
+            "type": "string"
+          }
+        }
+      }
     }
   },
   "paymentMethodRead": {

package/dist/generated/schemas.d.ts

@@ -17181,17 +17181,17 @@ export declare const updatePcIdBody: z.ZodObject<{
 }>;
 export declare const reimbursementPolicyCreateBody: z.ZodObject<{
     name: z.ZodString;
-    electricityRateSource: z.ZodEnum<["policy", "charge_point"]>;
     validityStartsOn: z.ZodString;
     partnerId: z.ZodOptional<z.ZodNumber>;
     partnerContractId: z.ZodOptional<z.ZodNumber>;
     electricityRateId: z.ZodOptional<z.ZodNumber>;
     validityEndsOn: z.ZodOptional<z.ZodString>;
+    electricityRateSource: z.ZodEnum<["policy", "charge_point"]>;
     operatorId: z.ZodOptional<z.ZodNumber>;
 }, "strip", z.ZodTypeAny, {
     name: string;
-    electricityRateSource: "policy" | "charge_point";
     validityStartsOn: string;
+    electricityRateSource: "policy" | "charge_point";
     operatorId?: number | undefined;
     partnerId?: number | undefined;
     electricityRateId?: number | undefined;
@@ -17199,8 +17199,8 @@ export declare const reimbursementPolicyCreateBody: z.ZodObject<{
     validityEndsOn?: string | undefined;
 }, {
     name: string;
-    electricityRateSource: "policy" | "charge_point";
     validityStartsOn: string;
+    electricityRateSource: "policy" | "charge_point";
     operatorId?: number | undefined;
     partnerId?: number | undefined;
     electricityRateId?: number | undefined;
@@ -17209,8 +17209,8 @@ export declare const reimbursementPolicyCreateBody: z.ZodObject<{
 }>;
 export declare const reimbursementPolicyUpdateBody: z.ZodObject<{
     name: z.ZodOptional<z.ZodString>;
-    electricityRateSource: z.ZodOptional<z.ZodEnum<["policy", "charge_point"]>>;
     validityStartsOn: z.ZodOptional<z.ZodString>;
+    electricityRateSource: z.ZodOptional<z.ZodEnum<["policy", "charge_point"]>>;
     partnerId: z.ZodOptional<z.ZodNumber>;
     partnerContractId: z.ZodOptional<z.ZodNumber>;
     electricityRateId: z.ZodOptional<z.ZodNumber>;
@@ -17219,18 +17219,18 @@ export declare const reimbursementPolicyUpdateBody: z.ZodObject<{
     name?: string | undefined;
     partnerId?: number | undefined;
     electricityRateId?: number | undefined;
-    electricityRateSource?: "policy" | "charge_point" | undefined;
     validityStartsOn?: string | undefined;
     partnerContractId?: number | undefined;
     validityEndsOn?: string | undefined;
+    electricityRateSource?: "policy" | "charge_point" | undefined;
 }, {
     name?: string | undefined;
     partnerId?: number | undefined;
     electricityRateId?: number | undefined;
-    electricityRateSource?: "policy" | "charge_point" | undefined;
     validityStartsOn?: string | undefined;
     partnerContractId?: number | undefined;
     validityEndsOn?: string | undefined;
+    electricityRateSource?: "policy" | "charge_point" | undefined;
 }>;
 export declare const rfidTagCreateDeprecatedBody: z.ZodObject<{
     id: z.ZodOptional<z.ZodNumber>;

package/dist/generated/schemas.js

@@ -4539,12 +4539,12 @@ export const updatePcIdBody = z.object({
 // POST /public-api/resources/reimbursement-policies/v1.0
 export const reimbursementPolicyCreateBody = z.object({
     name: z.string().max(255),
-    electricityRateSource: z.enum(["policy", "charge_point"]),
     validityStartsOn: z.string(),
     partnerId: z.number().int().optional(),
     partnerContractId: z.number().int().optional(),
     electricityRateId: z.number().int().optional(),
     validityEndsOn: z.string().optional(),
+    electricityRateSource: z.enum(["policy", "charge_point"]),
     operatorId: z.number().int().optional()
 });
 // GET /public-api/resources/reimbursement-policies/v1.0/{reimbursementPolicy}
@@ -4552,8 +4552,8 @@ export const reimbursementPolicyCreateBody = z.object({
 // PATCH /public-api/resources/reimbursement-policies/v1.0/{reimbursementPolicy}
 export const reimbursementPolicyUpdateBody = z.object({
     name: z.string().max(255).optional(),
-    electricityRateSource: z.enum(["policy", "charge_point"]).optional(),
     validityStartsOn: z.string().optional(),
+    electricityRateSource: z.enum(["policy", "charge_point"]).optional(),
     partnerId: z.number().int().optional(),
     partnerContractId: z.number().int().optional(),
     electricityRateId: z.number().int().optional(),