CreatePortfolioCommentRequest
| Field | Type |
|---|---|
portfolio_id | string |
body | string |
attachment_file_ids | repeated string |
Required scope: portfolio_comment:create
Comments with one or more attachmentFileIds additionally require the exact
portfolio_file:read scope.
Use this endpoint to add an internal memo or comment to a portfolio. The body uses the same reference and file-token format as the portfolio UI:
@[type:id:Display label][filename.pdf](file:file-id)Supported UI reference types include member, problem, document, photo,
internal_file, payment, refund, order, offer, action_request, and
flow. Use IDs the API-key creator can access. Labels are display text, not an
authorization boundary.
Upload files first, complete the upload, then include each file ID in
attachmentFileIds. A file token controls where it renders in the body; the
attachment list creates the canonical comment-to-file association.
POST /public-api/publicapi.v1.Portfolio/CreatePortfolioComment Creates an internal portfolio comment/memo.
| Field | Type |
|---|---|
portfolio_id | string |
body | string |
attachment_file_ids | repeated string |
| Field | Type |
|---|---|
comment | PortfolioComment |
{ "portfolioId": "be85f4d1-b680-4964-bf62-9828fdf4ce04", "body": "Assigned to @[member:7fbbcbb2-c6d1-4b71-9864-d217494b6ef0:Alex Example]. See [inspection.pdf](file:cba8fef4-4fd2-4be6-af77-326e716ef130)", "attachmentFileIds": [ "cba8fef4-4fd2-4be6-af77-326e716ef130" ]}{ "comment": { "id": "a2ec8aef-691a-4e9d-b4fd-52e255883c6c", "portfolioId": "be85f4d1-b680-4964-bf62-9828fdf4ce04", "body": "Imported note from ERP", "attachments": [ { "id": "cba8fef4-4fd2-4be6-af77-326e716ef130", "kind": "PUBLIC_PORTFOLIO_ATTACHMENT_KIND_DOCUMENT" } ] }}