Skip to main content
POST/api/public/v1/profiles/{id}/sync/release

profiles.sync.release

Drop the unsynced data a lost or wiped machine still holds for this profile so it can open elsewhere from the latest revision (audited).

Capability: sync.recoverCommand (idempotent)DestructiveMCP tool: profiles_sync_release
View as Markdown

Parameters

NameTypeRequiredDescription
idpathstring (uuid)YesProfile id
command_idbodystring (uuid)YesClient-generated UUID for this command. Send the same id (and body) again to get the stored receipt instead of a second change; a different body under the same id is CONFLICT.
device_idbodystring (uuid)YesMachine that holds the unsynced data

Examples

curl -X POST "https://browlix.com/api/public/v1/profiles/<id>/sync/release" \
  -H "Authorization: Bearer $BROWLIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"command_id":"<uuid>","device_id":"<device_id>"}'

Response

201 with { data, replayed: false, correlation_id } the first time; 200 with replayed: true when the same command_id and body come again.

The field list of this reply is not published yet; read data as JSON.

Errors

CodeHTTPRetryable
UNAUTHENTICATED401No
FORBIDDEN403No
RATE_LIMITED429Yes
VALIDATION_FAILED422No
NOT_FOUND404No
CONFLICT409No
OUTCOME_UNKNOWN202Yes
DEPENDENCY_UNAVAILABLE503Yes
UNKNOWN500No

Every error code and when to retry

All operations