Set Reconciliation Policy

post/extensions/roboledger/{graph_id}/operations/set-reconciliation-policy

Change how much the close cares about one reconciliation: whether the period's close waits on it (required_for_close); its materiality, the difference up to which it still counts as reconciled; whether the close also waits for a sign-off (review_required); and whether the reviewer must be someone other than the person who ran the comparison (separate_reviewer, which can only be turned on while the graph has at least two members who can write; if it later has one, turn it off or add a member). Omitted fields keep their value. The next refresh-reconciliations uses the new materiality; comparisons already recorded are not re-judged.

Idempotency: supply an Idempotency-Key header to make safe retries; replays within 24 hours return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.

Authentication

Authenticate in any one of these ways — not all of them:

API key in the X-API-Key header.
Bearer token in the Authorization header.

Path parameters

Name	Type	Description
`graph_id`required	string	Graph Id Constraints: matches `^(kg[a-f0-9]{16,}(?:_[a-zA-Z0-9]{1,20})?\|sec(?:_[a-zA-Z0-9]{1,20})?\|library)$`

Header parameters

Name	Type	Description
`Idempotency-Key`optional	string	Idempotency-Key

Request body

Required, application/json.

Field	Type	Description
`structure_id`required	string	The reconciliation block.
`required_for_close`optional	boolean	Whether the period's close waits on it. Omit to keep.
`materiality`optional	number	A difference up to this amount still counts as reconciled. Omit to keep. Constraints: at least 0
`review_required`optional	boolean	Whether the close also waits for a sign-off, not just for the two sides to reconcile. Omit to keep.
`separate_reviewer`optional	boolean	Whether the person who signs off must be someone other than the person who ran the comparison. It can only be turned on when the graph has at least two members who can write. Omit to keep.

Example request

curl

curl -X POST "https://api.robosystems.ai/extensions/roboledger/{graph_id}/operations/set-reconciliation-policy" \
  -H "X-API-Key: $ROBOSYSTEMS_API_KEY" \
  -H "Idempotency-Key: <Idempotency-Key>" \
  -H "Content-Type: application/json" \
  -d '{
  "structure_id": "string"
}'

Responses

200 Successful Response

Field Type Description

operationrequired

string

Kebab-case operation name

operationIdrequired

string

op_-prefixed ULID for audit and SSE correlation

statusrequired

string

Operation lifecycle state

One of: completed, pending, failed

resultoptional

ReconciliationPolicyResponse

Command-specific result payload

ReconciliationPolicyResponse fields

Field	Type	Description
`structure_id`required	string
`required_for_close`required	boolean
`materiality`required	number
`review_required`required	boolean
`separate_reviewer`required	boolean

atrequired

string

ISO-8601 UTC timestamp

createdByoptional

string

User ID that initiated the operation

idempotentReplayoptional

boolean

True when this envelope came from the idempotency cache — the underlying command did not execute again. False on fresh executions.

Default: false

Status	Meaning
400	Invalid request
401	Authentication required
403	Access denied
404	Resource not found
409	Idempotency-Key conflict — key reused with different body
422	Validation error
429	Rate limit exceeded
500	Internal server error