---
title: "Delete Publish List"
method: POST
path: "/extensions/roboledger/{graph_id}/operations/delete-publish-list"
tags: ["RoboLedger: Report Distribution"]
---

# Delete Publish List

`POST /extensions/roboledger/{graph_id}/operations/delete-publish-list`

## 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/delete-publish-list`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Delete a publish list and its membership rows. Reports previously shared via this list are not affected — each share is an independent copy in the recipient's graph.

**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.

## Path parameters

- `graph_id` string, required

## Headers

- `Idempotency-Key` string, nullable

## Request body

- DeletePublishListOperation: Delete a publish list. All membership rows are removed; reports previously shared via this list are not affected (each share is an independent copy in the recipient's graph).
  - `list_id` string, required: The publish list to delete.

## Response `200`

Successful Response

- OperationEnvelopeDeleteResult
  - `operation` string, required: Kebab-case operation name
  - `operationId` string, required: op_-prefixed ULID for audit and SSE correlation
  - `status` 'completed' | 'pending' | 'failed', required: Operation lifecycle state
  - `result` DeleteResult: Shared response shape for delete / soft-delete operations. `deleted=True` means the operation succeeded (a row was deleted or flipped). A row that never existed gets a 404 — this shape never carries "not found". Defined once here, and used by both roboledger and roboinvestor, so the OpenAPI components key resolves to a single schema.
    - `deleted` boolean, required: `true` when the row was deleted in this call. Always `true` today — 404 covers the not-found case at the HTTP layer rather than via this field.
  - `at` string, required: ISO-8601 UTC timestamp
  - `createdBy` string, nullable: User ID that initiated the operation
  - `idempotentReplay` boolean: True when this envelope came from the idempotency cache — the underlying command did not execute again. False on fresh executions.

## Other responses

- `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

---

[API](https://skmtc.dev/robosystems/apis/robosystems-api.md) · [All operations](https://skmtc.dev/robosystems/apis/robosystems-api/llms.txt) · [OpenAPI document](https://skmtc.dev/robosystems/apis/robosystems-api/revisions/e661e2d5ca6a?raw)