1. Change Charge Point PIN with a PATCH request
   Fixed an issue where PIN property could not be updated to an existing Charge Point resource via API PATCH request:
   cURL

   curl --location --request PATCH 'https://{{baseUrl}}/public-api/resources/charge-points/v1.0/{{chargePointId}}' \
   --header 'Content-Type: application/json' \
   --header 'Accept: application/json' \
   --header 'Authorization: Bearer {{bearerToken}}' \
   --data '{
     "pin": "<string>"
   }'
   

1. Smart Charging details in Charge Point resource
   Smart Charging object is added to the Charge Point V2.0 resource. Please refer to the API Documentation for a detailed overview of the object structure
2. UserChangeNotification Webhook callback fix
   User's externalId property has been added to the UserChangeNotification webhook payload.
   

1. Certificate Actions added to Chargepoint resource: AMPECO Public API is now capable of managing Security Certificate actions for Chargepoints
   Install Certificate (https://{{baseUrl}}/public-api/actions/charge-point/v2.0/{chargePoint}/install-certificate)
   
   Get Installed Certificates (https://{{baseUrl}}/public-api/actions/charge-point/v2.0/{chargePoint}/sync-certificates)
   
   Delete Certificate (https://{{baseUrl}}/public-api/actions/charge-point/v2.0/{chargePoint}/delete-certificate)
   
2. New Authorisation Notification Webhook:
   1. Deprecate "AuthorizationNotification" callback
   2. Introduce "authorization.changed" callback

1. Better Distinguishment of Extended Sessions
   Deprecating the previous property extendingSessionId. Add the following properties to the Sessions endpoint:

   originalSessionId
   integer or null
   Description: Session ID of the session that the current extended session is extending.

   extendedBySessionId
   integer or null
   Description: Id of the session that extends this session.

Enhanced Public API with Get Security Log Action for All Charge Points
We've enhanced our Public API to include the "Get Security Log" action for Charge Points, allowing users to retrieve the Security Events log in compliance with UK Electric Vehicles Smart Charge Points (EVSCP) regulations and mirroring functionality already present in our mobile app. The new action introduces parameters including a required charge-point ID, a log-fetching URL, a timestamp to filter logs, an interval for retry attempts and a reason for log retrieval; it can be located under Action/Charge Point.