Skip to main content
The SDK’s releases are also on GitHub, with the full list of changes. See Versions for what each kind of version means.
Chargers
11 November 2026
  • The Volt Time Two Pro: added with its serial number and pincode like other Volt Time chargers, then checked over Bluetooth with its Bluetooth PIN, also when it’s already online. Link corrects its OCPP address when it’s wrong and shows its connections, and your user can give it a Wi-Fi network or a SIM’s APN. In your app or in Chrome and Edge (reconnect needs ble).
  • No new SDK version needed.
Chargers
11 November 2026
  • The Charge Amps Halo: set up over the charger’s own hotspot after a restart at its breaker, with the serial number and PIN on its label. In your app (local_hotspot, needs wifi, socket).
  • The charger keeps its Chargepoint ID and its current operator, and Charge Amps’ cloud stays connected as Data & control. Link shows its connections, can give it a Wi-Fi from the charger’s own scan, and restarts it onto Plugchoice.
  • No new SDK version needed.
SDK API
2 November 2026
  • Every transaction has its meter readings, meter_start_kwh and meter_stop_kwh, whether the stop reading was estimated (meter_stop_estimated), and is_mid: whether the charger has a MID-certified meter. Filter on charger_id, from and to for one charger’s transactions in a period.
Chargers
28 October 2026
  • The Webasto Next: set up over the charger’s own hotspot, from the label in its manual. In your app (local_hotspot, needs wifi, lan).
  • The charger keeps its Chargepoint ID, its serial number, and its current operator. Link shows its connections and can connect it to a Wi-Fi network.
  • No new SDK version needed.
Chargers
27 October 2026
  • go-e Chargers, the PRO, Gemini, Gemini flex, Core and HOME: set up over the charger’s own hotspot, from the reset card that comes with it. In your app (local_hotspot, needs wifi, lan, socket).
  • The charger keeps its Chargepoint ID and its current operator. Link shows its connections, with the mobile network it’s on, and can give it a Wi-Fi from the charger’s own scan. Plugchoice imports its charging history from go-e’s cloud.
  • Finalize takes history_export, where a charger’s brand’s cloud keeps its history, and reads the sessions from there.
  • No new SDK version needed.
Chargers
27 October 2026
  • Teltonika TeltoCharges, the TeltoCharge and the EVC 2: set up over Bluetooth, paired with the last 6 digits of the installer code on the charger’s sticker. In your app (local_ble, needs ble).
  • The charger keeps its Chargepoint ID and its current operator. Link imports its charging history, and its RFID cards when it isn’t on OCPP yet, shows its connections and can give it a Wi-Fi from the charger’s own scan.
  • No new SDK version needed.
Chargers
27 October 2026
  • Wallbox chargers, such as the Pulsar Plus, Pulsar Max, Pulsar Pro and Quasar: set up over Bluetooth, paired with the passcode the Wallbox app shows in its Charger info. In your app (local_ble, needs ble).
  • The charger keeps its Chargepoint ID and its current operator. Link imports its charging history, shows its connections and can give it a Wi-Fi from the charger’s own scan.
  • No new SDK version needed.
SDK API
27 October 2026
  • is_mid on every charger: whether it has a MID-certified meter. null when Plugchoice doesn’t know its model, or whether that model has one.
Chargers
27 October 2026
  • Enovates chargers, such as the ENO one: set up over the charger’s own hotspot, from the ENO install code on the label in its installation guide. In your app (local_hotspot, needs wifi and socket).
  • Your user restarts the charger first: it only opens its hotspot when it starts.
  • The charger keeps its Chargepoint ID and its current operator. Link shows its connections and can give it a Wi-Fi or change its mobile settings.
  • No new SDK version needed.
Hosted flow
27 October 2026
  • When you give a whole location on the client session, Link no longer shows the address screen before signing in.
  • Link skips the model picker when every model of the brand is added the same way.
  • No new SDK version needed.
SDK APIHosted flow
20 October 2026
  • Meter readers: a client session with device_type: "meter" adds a meter reader to a site instead of a charger.
  • The Reduxi P1 Ultra, set up over its own hotspot in your app (local_hotspot, needs wifi and tcp).
  • Chargee Sparky and Flint, added by the code on the reader, also in a browser (vendor_cloud).
SDK API
19 October 2026
  • List transactions and get a transaction: the charging sessions of the chargers your team owns, and of your users’ chargers they let you read (sessions:read). One still charging is active, with the energy so far. The card used is a hash per integration.
Hosted flow
17 October 2026
  • When the charger goes to your user’s own Plugchoice account, your user sets it up first and signs in after, to save it to one of their sites or a new one. A link session that ends without signing in releases the charger.
  • No new SDK version needed.
PlugchoiceSDK API
16 October 2026
  • Settings > SDK in Plugchoice, for teams with access to the SDK. Team admins fill in the profile for the consent screen with a logo, set each integration’s accent colour and Return URLs, and rotate the secret: the previous one keeps working for 24 hours.
  • Every member sees your customers, the chargers users shared with you, and the link sessions. Admins can delete a customer.
  • Chargers your users shared with you show in your team’s charger list.
  • Plugchoice gives a team access to the SDK. Without it, its integrations get 403 sdk-access-required.
SDK APIHosted flow
16 October 2026
  • By default, a charger your user adds goes to their own Plugchoice account, and your integration gets a grant with the scopes they agreed to. Plugchoice can set an integration up so the chargers go to your team instead. See Client sessions and scopes.
  • Your user signs in to their Plugchoice account during the link session, or creates one, with a code by email, Google or Apple.
  • consent_scopes on the client session: what the consent screen asks for, within what Plugchoice allowed your integration. charger:read is always asked. A user is asked again when you ask for more.
  • email on the client session prefills signing in.
  • Your user can share a charger they already have in their account. In a browser, a charger only an app can set up goes to the Plugchoice app, and Link waits until it shows up in their account.
  • access on every charger: partner for one your team owns, user with the scopes for one shared with you. A shared charger has no site_id.
  • Your profile and its review by Plugchoice, shown on the consent screen (profile-incomplete until it’s reviewed).
SDK API
16 October 2026
  • Remove a charger (DELETE /chargers/{charger_id}): a user’s charger only loses your access and stays in their account; one your team owns is released.
  • Remove a customer (DELETE /customers/{external_user_id}): ends your access to their chargers, releases the ones your team holds for them, and forgets the external_user_id.
  • Both answer 204, also for one that’s gone, so retrying is safe.
Chargers
9 October 2026
  • The Volt Time Source and Source 2 and the Ratio io7, set up through the charger’s own web app as its Installer, on the home network or the charger’s setup network. In your app.
  • A Source 2 signs in with the serial number and pincode on its card, a Source with its serial number and the Installer password on its sticker.
  • The mobile settings show the SIM’s ICCID.
  • No new SDK version needed.
Chargers
9 October 2026
  • Ratio io5 and io6, over Bluetooth in your app: your user picks theirs from the chargers nearby, and the phone asks for the passcode on its sticker when it pairs. A browser can’t pair with it, so there Link offers your app or setting it up by hand. Other Ratio models are set up by hand.
  • ratio for vendor on the client session.
  • No new SDK version needed.
Hosted flow
8 October 2026
  • The charger’s connections have screens of their own: each connection with its state, address and signal, the Wi-Fi networks from the charger’s own scan on the next screen, and a network’s password after that. The screen keeps itself up to date.
  • Where the charger has that setting (SolarEdge), your user picks the one connection it uses.
  • No new SDK version needed.
ChargersSDK API
8 October 2026
  • Easee: your user signs in to Easee, or confirms Plugchoice in the Easee app, and Plugchoice becomes the charger’s operator. Works in a browser too.
  • SolarEdge ONE EV Chargers, added from their sticker over Bluetooth, in your app or in Chrome and Edge.
  • No new SDK version needed for either.
  • A new onboarding method, local_ble, for methods on the client session.
SDK
7 October 2026
  • iOS: a privacy manifest (PrivacyInfo.xcprivacy), so Xcode includes the SDK in your app’s privacy report. The SDK doesn’t track and uses none of the APIs Apple asks a reason for.
  • The first version on Maven Central.
SDK
7 October 2026
The first public version of the Plugchoice SDK, in beta.
  • Three platforms, one version: iOS (PlugchoiceSDK, Swift Package Manager), Android (com.plugchoice:plugchoice) and React Native (@plugchoice/react-native, with an Expo config plugin).
  • Link, the guided charger setup: add a charger, change its network, set it up, or reconnect it, opened with an action from your app.
  • One callback for client secrets: the SDK asks your app for a client secret when Link opens and whenever it needs a new one, passing the action so your server can scope it.
  • Native tools for the hosted flow: Wi-Fi hotspot joins, local network discovery and sessions, Bluetooth LE, raw TCP and UDP, and QR scanning.
  • transports() tells you what the device can do, to compare with a charger’s capabilities.
SDK API
7 October 2026
The first version of the SDK API at https://api.plugchoice.com/sdk/v1.
  • Client sessions with a required scope, for your users (external_user_id) or your own chargers.
  • Link sessions, to confirm on your server what a time through Link did.
  • Chargers with their capabilities.
  • Date versions in the Plugchoice-Version header, and errors as problem details.