Skip to main content
When a client session is for one of your users (external_user_id), their link session asks them to agree before it adds or shares a charger. The consent screen tells them that you use Plugchoice to connect to their chargers, and lists what you may do, one line per scope the link session asks for:
  • When your integration adds chargers to your users’ own Plugchoice accounts, the link session asks for the scopes in the client session’s consent_scopes, or for every scope Plugchoice allowed your integration when you leave it out. The screen also says “Your charger stays yours. Acme Energy only gets what you allow here.”
  • When your team owns your users’ chargers, it asks for charger:read and charger:control.
  • It says your user can disconnect at any time. In Plugchoice, a charger’s Apps page lists the apps with access to it, and removes one.
  • The footer says the Plugchoice End User Terms apply and links the Plugchoice Privacy Policy, plus your privacy policy and terms when your profile has them.
  • Agree and continue records the consent and goes on.
  • Not now ends the link session: it is abandoned with abandon_reason: consent_declined, and your app gets cancelled.
  • A user who agreed once isn’t asked again in later link sessions with your integration, until the consent text changes or a link session asks for a scope they didn’t agree to.
  • Your own chargers (no external_user_id) and Plugchoice users’ own link sessions have no consent screen.
For a charger in your user’s own account, your integration gets a grant with the scopes they agreed to, and nothing else. Get a charger shows them in access.scopes.
  • sessions:read lets you list the charger’s transactions. Without it, Get a transaction is 403 scope-missing.
  • charger:control lets you open setup and reconnect link sessions on the charger. One integration controls a charger at a time. When another app has control, Link asks your user whether your app takes it over. If they keep it with the other app, your grant gets the other scopes, or none at all when Plugchoice set your integration up as one that needs control (control-held).
  • To get a scope later, start an add link session with it in consent_scopes. Your user agrees again and shares the charger again.

Your branding

Link shows your brand wherever your users see it:
A team admin fills these in under Settings > SDK in Plugchoice: the name, legal name, privacy policy and terms URLs, a support email or page, and a logo (PNG, JPG or WebP, up to 1 MB) on the Profile tab, and the accent colour as #RRGGBB in each integration’s settings. The logo and accent colour are optional; without an accent colour Link uses its own. Plugchoice reviews your profile once, when it gives your team access to the SDK. Changes you make after that show at once. Until the profile is reviewed and has a support email or page, link sessions for your users don’t start (profile-incomplete).

Light, dark and language

Each client session sets:
  • color_scheme: light, dark, or system (the default), which follows the phone. Send the one your app uses, so Link matches it.
  • language: de, en, es, fi, fr, nl or zh. Other languages fall back to English.
See Client sessions and scopes.