In a browser

Link also runs in a browser, on a phone or a computer. Use it from your web app or customer portal. There’s no SDK to install: your server creates a client session and sends the browser to its web_url.

Open Link

Create a client session

Your server creates a client session for your user, as in Get started, scoped to what the user is about to do. Add a redirect_uri to send the user back when they’re done.

Send the browser to web_url

The answer’s web_url already holds the client secret. For an action other than add, append the action and its charger. For add at one of the scope’s sites, append site_id.

Confirm the outcome

When the user comes back, your server confirms the link session with Get a link session.

server.ts

app.get('/chargers/:chargerId/network', requireUser, async (req, res) => {
  const { chargerId } = req.params;
  const response = await fetch('https://api.plugchoice.com/sdk/v1/client-sessions', {
    method: 'POST',
    headers: {
      // Your integration's access token, as in Get started.
      Authorization: `Bearer ${await plugchoiceToken()}`,
      'Content-Type': 'application/json',
      'Plugchoice-Version': '2026-10-07',
    },
    body: JSON.stringify({
      external_user_id: req.user.id,
      scope: { chargers: [chargerId] },
      redirect_uri: 'https://app.example.com/plugchoice/done',
    }),
  });
  if (!response.ok) throw new Error(`Plugchoice: HTTP ${response.status}`);
  const { web_url } = await response.json();

  res.redirect(`${web_url}&action=network&charger_id=${encodeURIComponent(chargerId)}`);
});

The parameters go in the URL’s fragment, after #:

Parameter
`cs`	The client secret. `web_url` has it already.
`action`	`add` (the default), `network`, `setup`, `reconnect`, or a later one. See Actions.
`charger_id`	The charger, for every action but `add`.
`site_id`	For `add`: one of the scope’s sites.

The client secret in the URL

Browsers never send a URL’s fragment to a server, so the secret doesn’t reach server logs or a Referer header. The hosted flow reads it and removes it from the address bar at once. If the user reloads the page, the link session carries on. In a browser, Link can’t ask your app for a new secret, as the mobile SDK does. Open web_url within 60 minutes of creating the client session, or the user sees an error. Create a new client session for every visit rather than storing the URL. Once open, a link session lasts up to 6 hours.

When the user is done

With a redirect_uri, the hosted flow sends the browser there, with two query parameters added:

Parameter
`status`	`success`, `cancelled` or `error`
`session_id`	The link session

https://app.example.com/plugchoice/done?status=success&session_id=0b8a6f3e-1c2d-4e5f-8a9b-0c1d2e3f4a5b

Anyone can type these parameters, so don’t trust them. Read the outcome with Get a link session, and show what it says. Without a redirect_uri, the hosted flow tells the user they can close the page.

A redirect_uri must be on your integration’s allow-list. To add one, email support@plugchoice.com.

What works in a browser

A browser can’t join a charger’s Wi-Fi or reach chargers on the local network, so some setups need the mobile SDK. In a browser, the hosted flow only offers what it can do there.

Charger	In a browser	In your app with the SDK
Volt Time	Added by serial number and pincode. Wi-Fi over Bluetooth in Chrome and Edge.	Everything, including Wi-Fi over Bluetooth
Zaptec	Yes: the owner signs in with their Zaptec account	Yes
Alfen	Only set up by hand	Guided setup on the home Wi-Fi
Peblar	Only set up by hand	Guided setup over the charger’s own Wi-Fi
Other OCPP chargers	Set up by hand	Set up by hand

Bluetooth in a browser works in Chrome and Edge on Android, Windows, macOS and ChromeOS. It doesn’t work in Safari, so not in any browser on an iPhone, nor in Firefox. There, the hosted flow skips the Wi-Fi step and waits for the charger to come online another way, such as a network cable or a SIM. In Chrome or Edge, the browser asks which device to use: the user taps Connect, then picks the charger, which is named after its Chargepoint ID.

Get started

Platforms

Concepts

Chargers

API reference

Errors

Resources

Open Link

The client secret in the URL

When the user is done

What works in a browser

​Open Link

​The client secret in the URL

​When the user is done

​What works in a browser

Open Link

The client secret in the URL

When the user is done

What works in a browser