RoboLedger: Reports

Transition Filing Status

Move a Report along the non-file legs of the filing lifecycle (draft ↔ under_review, filed ↔ archived). Archiving takes a filed report off the current list without deleting it; unarchiving returns it to 'filed'. Use 'file-report' to file a draft so audit fields land cleanly.

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/transition-filing-status

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/transition-filing-status
  • Auth: one of:
    • API key in header X-API-Key
    • HTTP bearer

Path parameters

graph_idstring required

Headers

Idempotency-Keystring nullable

Request body

report_idstring required

The Report to transition.

target_statusstring required

Target lifecycle state: under_review (submit a draft for review), draft (send it back), archived (take a filed report off the current list; it stays a record) or filed (unarchive). Filing a draft goes through file-report so audit fields land cleanly.

Example request

{
  "report_id": "rpt_01HVF8T0M2YTAY3BBNRH0V0",
  "target_status": "under_review"
}

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.