Skip to main content

Device pairing

Device pairing is how a Mac running BlueSender claims a seat on a license. The Mac performs pairing internally on launch and after each license-key change — there is no public HTTP surface a CRM integrator needs to call.

This page is a conceptual primer covering the parts of pairing that affect what an integrator can observe.

deviceId​

The Mac generates a stable deviceId (UUID) the first time it runs and reuses it for the lifetime of the install. Re-installing the app or wiping the keychain may produce a new deviceId, which counts as a new device against maxSeats until the old one is released.

The deviceId is internal to the licensing layer. CRMs do not see it on any public webhook.

maxSeats and seat management​

Each license has a maxSeats cap (set when the license is issued). A device claims one seat when its licenseKey is entered into the Mac app. The seat is held for as long as the device is paired.

If the user tries to pair a Mac on a license that already has maxSeats active devices, the Mac app surfaces a "you already have N of N devices" message and asks the user to release one before continuing. The Mac UI lists the existing devices (by their operator-assigned name) so the user can identify the one to free up.

Releasing a device​

Releasing a device — freeing the seat it occupies on a license — is an operator-side action, not part of the public integration contract today. End-users who need to free a seat (e.g. after replacing a Mac) should contact the BlueSender operator out-of-band. After release, the affected Mac's licenseKey re-entry will succeed with the seat available again.