Topolo Docs Topolo Platform
Open workspace

List draft attachments

List the private source documents attached to one journal draft.

Outcome

List the private source documents attached to one journal draft.

Before you start

  • Verify the intended environment, authenticated identity and specifically approved organization context.
  • The published application permission is journals:read. Discover the exact granted canonical Books workspace and bind it separately from action input.

Discover the target

topolo whoami --json
topolo actions get app_topolo_books.journals.drafts.attachments.list --detail --json
topolo resources topolo-books --json
topolo workspaces list topolo-books --json
  • Set BOOKS_WORKSPACE_ID to the exact granted workspace returned by discovery.
  • draftId: Exact draft.id from journals.drafts.list/get. Posting or discarding removes the mutable draft.

Request

GET /api/journal-drafts/{draftId}/attachments

Inspect and test this action. Save the reviewed input as payload.json; supply credential/resource context separately.

Input fields

FieldRequiredMeaningSchema and constraints
draftIdRequiredExact draft.id from journals.drafts.list/get. Posting or discarding removes the mutable draft.{"type":"string","minLength":1}

Inspect nested fields and the complete input schema.

Effects

  • Reads private attachment metadata for one editable journal draft.

Interpret the response

Read $.attachments[].id for the returned journal_attachment identifier. Empty collections and nullable fields do not discover a target.

Confirm every returned attachment belongs to the requested draft.

Inspect the success schema. CLI/MCP add their own transport envelope; CLI --detail requests the full result.

Worked examples

Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.

Run a reviewed request

Save the input from the selected worked example as payload.json. Validate and inspect the plan before calling the action; refused examples demonstrate errors and are not instructions to execute.

CLI:

topolo actions validate app_topolo_books.journals.drafts.attachments.list --data @payload.json --json
topolo actions plan app_topolo_books.journals.drafts.attachments.list --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_books.journals.drafts.attachments.list --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --detail --json

MCP tool and arguments for the first successful example:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_books.journals.drafts.attachments.list",
    "input": {
      "draftId": "jd_52ec4f8955f3410e931b83667f29a3c0"
    },
    "resourceType": "workspace",
    "resourceId": "<exact granted workspace id>",
    "detail": true
  }
}

Refused response · auth_error

Input · payload.json:

{
  "draftId": "jd_7f3c1b"
}

Captured response · HTTP 401

{
  "error": "API key validation failed"
}

HTTP 401. SDK error code auth_error. Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.

Successful response · HTTP 200

Input · payload.json:

{
  "draftId": "jd_52ec4f8955f3410e931b83667f29a3c0"
}

Captured response · HTTP 200

{
  "attachments": []
}

HTTP 200. Confirm every returned attachment belongs to the requested draft.

Successful response · HTTP 200

Input · payload.json:

{
  "draftId": "jd_ef8abf153ae14b6491d2a0374121e096"
}

Captured response · HTTP 200

{
  "attachments": [
    {
      "id": "jatt_fe0e6b7bfd6d4be3bceb5c3be7dd4556",
      "draft_id": "jd_ef8abf153ae14b6491d2a0374121e096",
      "journal_event_id": null,
      "file_name": "engagement-letter.pdf",
      "content_type": "application/pdf",
      "size_bytes": 16,
      "checksum_sha256": "f7711d1542c029371e0ad7159632c392465700aed13126774e9e8a9575b20078",
      "created_by": "usr_evidence",
      "created_at": "2026-10-05T19:42:51.577Z",
      "updated_at": "2026-10-05T19:42:51.577Z"
    }
  ]
}

HTTP 200. Confirm every returned attachment belongs to the requested draft.

Refused response · journal_draft_not_found

Input · payload.json:

{
  "draftId": "jd_ef8abf153ae14b6491d2a0374121e096"
}

Captured response · HTTP 404

{
  "error": "journal_draft_not_found",
  "message": "Journal draft jd_ef8abf153ae14b6491d2a0374121e096 does not exist in this workspace"
}

HTTP 404. SDK error code journal_draft_not_found. Read journals.drafts.list/get in this workspace. A posted or discarded draft no longer exists; follow the retained posted journal id when available.

Verify the result

  • Confirm every returned attachment belongs to the requested draft.

Errors and recovery

  • auth_error (HTTP 401): Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.
  • journal_draft_not_found (HTTP 404): Read journals.drafts.list/get in this workspace. A posted or discarded draft no longer exists; follow the retained posted journal id when available.

These are observed local refusals. Shared authentication, schema validation and resource authorization can also refuse before the route. Preserve the actual error, details and request id.

Recovery boundary

This action does not change service state.

  • Get journal draft: Read one editable journal draft with its ordered lines.
  • List journals: List posted journal events, filtered by date range or period, searched across description, reference and journal type, and sorted by sequence, posted date, description or amount. Newest first unless you say otherwise.

Evidence

Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.