Record a processed workspace-opening checkpoint so later openings show newer activity.

Record that activity through the exact opening snapshot has been processed. The checkpoint is the opening's data.new_since_checkpoint.checkpoint_candidate, also carried as args.checkpoint on the opening's open.acknowledge next action. An opening with nothing new records its own checkpoint and offers no acknowledgement. Later openings show newer activity; review areas stay until you record what came of them, and attention and due notes remain until resolved.

post/v1/open/acknowledge

Request

  • Base URL: https://api.candor.money
  • URL: https://api.candor.money/v1/open/acknowledge
  • Auth: HTTP bearer

Headers

Idempotency-Keystring required

Stable opaque identity for one logical POST. Reuse only with the same method, path, actor, and body for transport retries. A completed receipt replays its original result, including a refusal; changed input with the same key is rejected. After a refused action and access recovery, use a new key for the new attempt. Follow retryable and recovery guidance if the operation is still running or its outcome is unknown.

Request body

checkpointstring required

The exact checkpoint returned by an opening you have processed, from its data.new_since_checkpoint.checkpoint_candidate or the args.checkpoint of its open.acknowledge next action. Marks activity through that snapshot as seen across the workspace, without resolving attention or due notes. Later activity remains new.

Response

Workspace checkpoint acknowledgement envelope.

schema_versionstring required
generated_atstring date-time required
request_idstring required
status'success' | 'partial_success' | 'action_required' | 'error' required
user_messagestring

Optional concise user-safe message the calling agent may adapt.

warningsobject[] required
dataobject nullable required

Operation-specific result data, or null when the request ends in an error.

Changes

No recorded changes to this operation across all 1 revision of this API.