RoboLedger: Report Distribution

Unblock Source Graph

Lifts a block, allowing that graph to share reports into this one again. Reports removed by an earlier purge are not restored — unblocking reopens the channel, it does not undo. Requires the graph admin role: a block is a standing decision about who may write into this graph, so a member cannot reverse it over an admin's head. Returns 404 when the source was not blocked.

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.

post/extensions/roboledger/{graph_id}/operations/unblock-source-graph

Request

  • Base URL: https://api.robosystems.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.robosystems.ai/extensions/roboledger/{graph_id}/operations/unblock-source-graph
  • Auth: one of:
    • API key in header X-API-Key
    • HTTP bearer

Path parameters

graph_idstring required

Headers

Idempotency-Keystring nullable

Request body

source_graph_idstring required

Graph ID to unblock.

Example request

{
  "source_graph_id": "kg1a2b3c4d5e6f7a8b9c"
}

Response

Successful Response

operationstring required

Kebab-case operation name

operationIdstring required

op_-prefixed ULID for audit and SSE correlation

status'completed' | 'pending' | 'failed' required

Operation lifecycle state

atstring required

ISO-8601 UTC timestamp

createdBystring nullable

User ID that initiated the operation

idempotentReplayboolean

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

Changes

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