Skip to main content
The Plugchoice SDK is in beta. Until version 1.0, a minor version may change the SDK or the SDK API. Pin the SDK version in your app and the Plugchoice-Version header on your server.
Three parts move at their own pace: the SDK in your app, the hosted flow it shows, and the SDK API your server calls.

​
The SDK

The iOS, Android and React Native SDKs share one version number and are released together.
  • Versions follow semantic versioning. Releases are made with release-please from the repository’s conventional commits; each one has an entry in the changelog and on GitHub.
  • During the beta (0.x), a minor version (0.4 to 0.5) may change the SDK’s API. A patch version (0.4.0 to 0.4.1) only fixes. Pin the minor version: .upToNextMinor(from: "0.4.0") in Swift Package Manager, ~0.4.0 in npm, an exact version in Gradle.
  • From 1.0, a breaking change needs a new major version.

​
The hosted flow

The hosted flow at connect.plugchoice.com is always the newest version. It supports every SDK version still in use: it asks the SDK what it can do when it opens, and uses only what that SDK has. So without a new release of your app:
  • new charger brands and models, and fixes for them, reach your users;
  • a new action works through the SDK’s custom action before the SDK has a helper for it.
An SDK update brings new native tools (a new way to reach chargers, for example) and fixes in the SDK itself.

​
The SDK API

The SDK API is versioned by date. Send the version you built against in the Plugchoice-Version header:
  • Every response says which version answered, in the same header.
  • Without the header you get the newest version, which can change under you. Always send it.
  • An unknown version is 400 unknown-version.
  • The only version is 2026-10-07.
Within a version, Plugchoice may add fields, capabilities, actions and error codes. Ignore the ones you don’t know. Support periods for older SDK and API versions will be published before version 1.0.