Clavem

Deactivation

Deactivation removes one device's registration from a license key, which frees a seat so the customer can activate the same key on another computer.

How it works

The app sends the license key and the instance_id it received at activation. The server deletes that activation and lowers the device count by one. The next activation on a different machine can use the seat.

curl https://clavem.io/v1/licenses/deactivate \
  -d license_key="YOUR-LICENSE-KEY" \
  -d instance_id="47596ad9-a811-4ebf-ac8a-03fc7b6d2a17"
{
  "deactivated": true,
  "error": null,
  "license_key": { "status": "active", "activation_limit": 3, "activation_usage": 1 }
}

activation_usage is the count after removal. The values above are samples.

A worked case

A customer owns a key with a limit of 3. Their old laptop, desktop and a work machine are all active, so activation_usage is 3.

  1. They buy a new laptop and try to activate. The server answers 400 with This license key has reached the activation limit.
  2. On the old laptop they choose Deactivate in the app. Usage drops to 2.
  3. They activate the new laptop. Usage is 3 again, with a new instance id.

The seat count never went above the limit, and nobody wrote to the seller.

Edge cases

  • The instance id is gone for good. Validating with a removed id returns 404 instance_id not found. The app should clear its stored license and ask for the key again. Activating creates a new id.
  • The last device. When the final device is removed, an active license returns to inactive. The key is still valid for activation.
  • Wrong or repeated calls. Deactivating an id that is already removed returns 404 instance_id not found., and an unknown key returns 404 license_key not found.
  • A token the device already holds. A signed token says what the license looked like when it was issued. It does not record the deactivation. Delete the stored token when you deactivate, or a copy of it still verifies offline until its refresh_by date.
  • A machine that died. No call can come from it. The customer needs a path that does not depend on the old device.

Deactivation versus revocation

Deactivation frees one seat and leaves the license alone. Revocation disables the whole license for every device. Uninstalling the app does neither, unless your uninstaller makes the call.

How Clavem handles it

Clavem gives buyers a device page at /licenses/manage. They enter their key, see which devices use it and remove one. There is no account and no email round trip, so a lost or wiped computer does not need a support ticket. The seller can also see each activation, with its name and last-seen time, in the dashboard and in GET /v1/admin/licenses/:id.

The call itself needs no secret. See the API reference for the full error table, and license transfer for moving a license between people rather than machines.

Questions

Does deactivation cancel the license?

No. The key stays valid and keeps its other devices. Only one seat is freed. Ending the license itself is called revocation.

What if the customer can no longer open the old computer?

The app cannot send the call from a dead machine. The customer needs a way to remove the device from another computer, such as a device page that takes the key.