Deprecation of triggerBoostCharge and deleteBoostCharge APIs removal date extension

Overview

We are deprecating the triggerBoostCharge and deleteBoostCharge APIs and replacing them with a new single API updateBoostCharge.

We are aware that these endpoints are still being used, so we have extended the removal date until 26/01/2026.

Please update your implementation to use the new API.

Deprecation

The triggerBoostCharge and deleteBoostCharge APIs are being deprecated as they only supports one device associated with an account meaning multiple devices at a property couldn't be de-authenticated.

Whats new

The new updateBoostCharge API introduces the ability to either trigger or cancel a boost charge by deviceId rather than accountNumber, supporting multiple devices & device types.

Example Request

mutation UpdateBoostCharge($input: UpdateBoostChargeInput!) {
  updateBoostCharge(input: $input) {
    id
    provider
    deviceType
  }
}