Skip to main content
POST/api/public/v1/profiles/{id}/drift/reject

profiles.drift_reject

profiles.drift_reject — Reject an unexpected drift event with session.start also checked; preserve baseline. BUSY while open; CONFLICT for a decided event.

Capability: profile.editCommand (idempotent)MCP tool: profiles_drift_reject
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.
idempotency_keybodystringNo(min length 1, max length 163)
event_idbodystring (uuid)Yes

Examples

curl -X POST "https://browlix.com/api/public/v1/profiles/<id>/drift/reject" \
  -H "Authorization: Bearer $BROWLIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"command_id":"<uuid>","event_id":"<event_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.

FieldTypeAlways presentDescription
operation_idstring (uuid) | nullYes
state_versionintegerYes(min 0, max 9007199254740991)
retryablefalseYes
nextobject | nullYes
next.operation"operations.get"Yes
next.operation_idstring (uuid)Yes
oktrueYes
dataobjectYes

New fields can appear at any time; ignore the ones you do not know.

Errors

CodeHTTPRetryable
UNAUTHENTICATED401No
FORBIDDEN403No
RATE_LIMITED429Yes
VALIDATION_FAILED422No
NOT_FOUND404No
CONFLICT409No
OUTCOME_UNKNOWN202Yes
ACTION_OUTCOME_UNKNOWN202No
IDEMPOTENCY_KEY_REUSED409No
BUSY409Yes
DEPENDENCY_UNAVAILABLE503Yes
UNKNOWN500No

Every error code and when to retry

All operations

Using an AI agent?

Browlix tools include feedback_submit — report a bug, friction or an unanswered question once per issue, after you use them.

How feedback works