@ampeco/public-api-mcp 3.224.4 → 3.225.1

package/dist/generated/build-stats.json

@@ -1,13 +1,13 @@
 {
-  "totalEndpoints": 622,
-  "originalSize": 5344130,
-  "optimizedSize": 1523284,
-  "reductionPercent": 71.5,
-  "buildDuration": 1297,
+  "totalEndpoints": 623,
+  "originalSize": 5361903,
+  "optimizedSize": 1526638,
+  "reductionPercent": 71.53,
+  "buildDuration": 1273,
   "responseSchemas": {
-    "total": 622,
-    "withSchemas": 622,
-    "totalSchemaSize": 3050335,
-    "averageSchemaSize": 4904
+    "total": 623,
+    "withSchemas": 623,
+    "totalSchemaSize": 3064390,
+    "averageSchemaSize": 4919
   }
 }

package/dist/generated/endpoints.json

@@ -3861,6 +3861,36 @@
         }
       }
     },
+    {
+      "path": "/public-api/actions/partner-invoice/v1.0/{partnerInvoice}/issue-credit-note",
+      "method": "POST",
+      "operationId": "partnerInvoiceIssueCreditNote",
+      "summary": "Partner invoice / Issue credit note",
+      "description": "Issue a full credit note cancelling the given partner invoice. The credit note copies the original's seller, buyer, currency and payment terms, negates every line item, is marked paid, and references the cancelled invoice via `referenceId`. Only invoices generated through the built-in B2B invoice integration are eligible, and only one credit note may exist per invoice. Issuing returns the linked settlement report to `ready_to_invoice`. Partial credit notes are not supported. A `409` means the invoice is permanently ineligible and the request will not succeed on retry. It is returned when the invoice already has a credit note, when the target is itself a credit note, or when the invoice was not generated through the built-in B2B invoice integration.",
+      "tags": [
+        "action / partner invoice"
+      ],
+      "responses": {
+        "202": {
+          "description": "Accepted - the response body contains the newly created credit note"
+        },
+        "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 request could not be completed due to a conflict with the current state of the resource. The operation may succeed if retried."
+        },
+        "429": {
+          "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
+        }
+      }
+    },
     {
       "path": "/public-api/actions/partner-invoice/v1.0/{partnerInvoice}/update-external-id",
       "method": "POST",
@@ -3917,7 +3947,7 @@
       "method": "POST",
       "operationId": "partnerSettlementReportIssuePartnerInvoice",
       "summary": "Partner settlement report / Issue partner invoice",
-      "description": "This action validates the given settlement report and accepts it for partner invoice generation. The settlement report must have a B2B invoice processor configured on its operator, a non-negative balance (expenses >= revenue), and an invoice state that is either unset or `ready_to_invoice`. Invoice generation runs asynchronously after the request is accepted. Poll the settlement report read endpoint and check `invoiceState` and `partnerInvoiceId` for completion.",
+      "description": "This action validates the given settlement report and accepts it for partner invoice generation. The settlement report must have a B2B invoice processor configured on its operator, a non-negative balance (expenses >= revenue), and must not already have been invoiced. Invoice generation runs asynchronously after the request is accepted. Poll the settlement report read endpoint and check `partnerInvoiceId` for completion.",
       "tags": [
         "action / partner settlement report"
       ],
@@ -6129,6 +6159,9 @@
         "422": {
           "description": "The payload you provided is invalid"
         },
+        "424": {
+          "description": "The requested operation cannot be completed because it depends on communication with an external system (e.g., charge point) that is currently disconnected or unreachable"
+        },
         "429": {
           "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
         }
@@ -11363,6 +11396,12 @@
                 "powerOptions": {
                   "type": "object",
                   "properties": {
+                    "maxOutputVoltage": {
+                      "type": "integer",
+                      "minimum": 1,
+                      "maximum": 1000,
+                      "description": "Maximum output voltage for DC charging."
+                    },
                     "maxPower": {
                       "type": "integer",
                       "nullable": true,
@@ -11383,7 +11422,7 @@
                         "277"
                       ],
                       "nullable": true,
-                      "description": "The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
+                      "description": "The maximum intake (input) voltage of the EVSE. For the ac current type the output voltage is the same as this intake voltage, while for the dc current type the output voltage can differ and is exposed separately in maxOutputVoltage. The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
                     },
                     "maxAmperage": {
                       "type": "number",
@@ -11742,6 +11781,12 @@
                 "powerOptions": {
                   "type": "object",
                   "properties": {
+                    "maxOutputVoltage": {
+                      "type": "integer",
+                      "minimum": 1,
+                      "maximum": 1000,
+                      "description": "Maximum output voltage for DC charging."
+                    },
                     "maxPower": {
                       "type": "integer",
                       "nullable": true,
@@ -11762,7 +11807,7 @@
                         "277"
                       ],
                       "nullable": true,
-                      "description": "The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
+                      "description": "The maximum intake (input) voltage of the EVSE. For the ac current type the output voltage is the same as this intake voltage, while for the dc current type the output voltage can differ and is exposed separately in maxOutputVoltage. The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
                     },
                     "maxAmperage": {
                       "type": "number",
@@ -23262,6 +23307,12 @@
                 "powerOptions": {
                   "type": "object",
                   "properties": {
+                    "maxOutputVoltage": {
+                      "type": "integer",
+                      "minimum": 1,
+                      "maximum": 1000,
+                      "description": "Maximum output voltage for DC charging."
+                    },
                     "maxPower": {
                       "type": "integer",
                       "nullable": true,
@@ -23282,7 +23333,7 @@
                         "277"
                       ],
                       "nullable": true,
-                      "description": "The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
+                      "description": "The maximum intake (input) voltage of the EVSE. For the ac current type the output voltage is the same as this intake voltage, while for the dc current type the output voltage can differ and is exposed separately in maxOutputVoltage. The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
                     },
                     "maxAmperage": {
                       "type": "number",
@@ -23645,6 +23696,12 @@
                 "powerOptions": {
                   "type": "object",
                   "properties": {
+                    "maxOutputVoltage": {
+                      "type": "integer",
+                      "minimum": 1,
+                      "maximum": 1000,
+                      "description": "Maximum output voltage for DC charging."
+                    },
                     "maxPower": {
                       "type": "integer",
                       "nullable": true,
@@ -23665,7 +23722,7 @@
                         "277"
                       ],
                       "nullable": true,
-                      "description": "The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
+                      "description": "The maximum intake (input) voltage of the EVSE. For the ac current type the output voltage is the same as this intake voltage, while for the dc current type the output voltage can differ and is exposed separately in maxOutputVoltage. The maxVoltage of a charge point can fluctuate. Hence, when creating a charge point in the system, the maxVoltage is given as a range. For OCPI purposes it maps as follows: 220-240 = 230 110-130 = 120 400 = 400 380 = 380"
                     },
                     "maxAmperage": {
                       "type": "number",
@@ -37666,6 +37723,10 @@
                   "type": "integer",
                   "description": "Filter by the source settlement report ID."
                 },
+                "referenceId": {
+                  "type": "integer",
+                  "description": "Filter by the ID of the original partner invoice that a credit note cancels. Use this to find the credit note issued against a given invoice; combine with `type` to disambiguate. Matches nothing for regular invoices, which have no reference."
+                },
                 "paymentStatus": {
                   "type": "string",
                   "enum": [
@@ -37676,6 +37737,15 @@
                   "example": "unpaid",
                   "description": "Partner invoice payment status: - **unpaid**: No payment has been recorded against the invoice. - **partially_paid**: A payment has been recorded but the full amount is not yet covered. - **paid**: The full amount has been paid."
                 },
+                "type": {
+                  "type": "string",
+                  "enum": [
+                    "invoice",
+                    "credit_note"
+                  ],
+                  "example": "invoice",
+                  "description": "Partner invoice document type: - **invoice**: A regular partner invoice generated from a settlement report. - **credit_note**: A credit note that cancels an original partner invoice. Always references the cancelled invoice via `referenceId`."
+                },
                 "issuedFrom": {
                   "type": "string",
                   "format": "date",
@@ -38057,16 +38127,6 @@
                 "partnerId": {
                   "type": "integer"
                 },
-                "invoiceState": {
-                  "type": "string",
-                  "enum": [
-                    "ready_to_invoice",
-                    "in_progress",
-                    "invoiced"
-                  ],
-                  "example": "ready_to_invoice",
-                  "description": "Partner invoicing lifecycle state of a settlement report: - **ready_to_invoice**: The settlement report is approved and no partner invoice has been generated yet. - **in_progress**: A partner invoice has been requested or is being processed by the invoice processor. - **invoiced**: A partner invoice has been successfully generated from this settlement report."
-                },
                 "periodAfter": {
                   "type": "string",
                   "format": "date"
@@ -38104,6 +38164,9 @@
         "403": {
           "description": "You do not have permission to perform the action"
         },
+        "422": {
+          "description": "The payload you provided is invalid"
+        },
         "429": {
           "description": "Too many requests. Please try again later. For more information, please check the rate limit headers X-RateLimit-*"
         }
@@ -69337,7 +69400,7 @@
   ],
   "info": {
     "title": "Public API",
-    "version": "3.224.4",
+    "version": "3.225.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": [
@@ -69351,18 +69414,18 @@
       }
     }
   ],
-  "buildTimestamp": "2026-08-03T07:38:19.730Z",
+  "buildTimestamp": "2026-08-03T15:47:52.899Z",
   "stats": {
-    "totalEndpoints": 622,
-    "originalSize": 5344130,
-    "optimizedSize": 1523284,
-    "reductionPercent": 71.5,
-    "buildDuration": 1297,
+    "totalEndpoints": 623,
+    "originalSize": 5361903,
+    "optimizedSize": 1526638,
+    "reductionPercent": 71.53,
+    "buildDuration": 1273,
     "responseSchemas": {
-      "total": 622,
-      "withSchemas": 622,
-      "totalSchemaSize": 3050335,
-      "averageSchemaSize": 4904
+      "total": 623,
+      "withSchemas": 623,
+      "totalSchemaSize": 3064390,
+      "averageSchemaSize": 4919
     }
   }
 }