Devices

Start a browser enrollment (desktop app, no auth)

RFC 8252 native-app sign-in. The app sends only its public key, a PKCE S256 challenge and a loopback redirect_uri (http, 127.0.0.1 / localhost / [::1], any port, a path), then opens authorize_url in the system browser. The person signs in and approves there; the app redeems the code at /api/v1/device_enrollments/token. The person-facing approve and deny steps are human-JWT flows and are not documented here.

post/api/v1/device_enrollments

Request

  • Base URL: https://saltapp.ai
  • URL: https://saltapp.ai/api/v1/device_enrollments
  • Auth: none required

Request body

namestring required
platform'macos' | 'windows' required
public_keystring required
code_challengestring required

base64url SHA-256 of the code_verifier.

redirect_uristring
machine_idstring

Opaque, stable install id of this machine. Re-registering the same machine_id under the same owner reuses the same device (same id, new key, old api-keys revoked, open sessions ended). Without it, a device of the same name and platform that has no machine_id is reused.

Response

Created. Poll mode (no redirect_uri) answers request_id, mode "poll", public_fingerprint and expires_at instead of authorize_url.

request_idstring
authorize_urlstring
mode'poll'
public_fingerprintstring
expires_atstring

Changes

No recorded changes to this operation across all 3 revisions of this API.