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

# Create Publish List

`POST /extensions/roboledger/{graph_id}/operations/create-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/create-publish-list`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Create a publish list (a saved set of recipient graphs). Members are managed separately via add/remove-member operations.

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

- CreatePublishListRequest: Create a new publish list. Members are added separately via `add-publish-list-members`.
  - `name` string, required: Human-readable list name (must be unique per graph).
  - `description` string, nullable: Free-form description shown to list owners.

## Response `200`

Successful Response

- OperationEnvelopePublishListResponse
  - `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` PublishListResponse: Publish list summary — header metadata, no members.
    - `id` string, required: List identifier (ULID).
    - `name` string, required: Human-readable list name.
    - `description` string, nullable: Free-form description.
    - `member_count` integer: Number of recipient graphs currently on the list.
    - `created_by` string, required: User ID that created the list.
    - `created_at` string, date-time, required: When the list was created.
    - `updated_at` string, date-time, required: Last metadata update (name/description).
  - `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)