HomeGuidesAPI ReferenceChangelog
Terms of Use
Changelog
Terms of Use
Start typing to search…
Back to All

Release Notes: Public API of AMPECO Charge 3.145.0

about 16 hours ago by ReadMe API
  1. ✨ New features
    1. Added new POST /public-api/actions/tax/v1.0/validate-vat endpoint to validate EU VAT numbers against the official VIES service. Accepts a countryCode and vatNumber in the request body, and returns the company name and address when available.
    2. Added new PATCH /public-api/resources/partner-contracts/v1.0/{partnerContract} endpoint for partial updates to partner contracts. Supports updating contract details, access permissions, revenue sharing configuration, and monthly platform fees.
    3. Added the optional locale request property to POST /public-api/actions/transactions/v1.0/{transaction}/issue-invoice. When bilingual invoicing is enabled for the operator, this controls the secondary language of the generated invoice.
    4. Added the optional allowChargingOutsideWorkingHours boolean property to the workingHours object on Location v2.0 endpoints (POST /public-api/resources/locations/v2.0, GET /public-api/resources/locations/v2.0, GET /public-api/resources/locations/v2.0/{location}, PATCH /public-api/resources/locations/v2.0/{location}). When enabled, charging sessions can start outside working hours even though the location appears as closed.
    5. Added the optional nullable companyName property to User endpoints on both v1.0 and v1.1 (GET /public-api/resources/users/v1.0, POST /public-api/resources/users/v1.0, GET /public-api/resources/users/v1.0/{user}, PATCH /public-api/resources/users/v1.0/{user}, and equivalent v1.1 endpoints). Available as company_name in request bodies and companyName in responses.
  2. 🔧 Improvements
    1. Expanded the notification type enum with the new FirmwareStatusNotification value across all Notifications v1.0 and v2.0 endpoints. Consumers can now subscribe to and receive firmware status change notifications.
    2. Expanded the keyResource/resourceType enum on Issues v1.0 endpoints (GET /public-api/resources/issues/v1.0, POST /public-api/resources/issues/v1.0, PATCH /public-api/resources/issues/v1.0/{issue}) with the new integration value. Issues can now reference integration resources.