Import 1–100 comments into a comment thread, appended in array order.
Posting is addressed by fund + thread together: obtain a threadId from ListCommentThreads (existing conversations) or CreateOrGetCommentThread (the order's general thread, created on demand), and pass it with the fund it belongs to — a threadId outside the fund is a 404. The comments are authored by the service account; onBehalfOf is display attribution only.
Mentions. body is plain text with mention tokens: @[[email protected]] mentions a fund member by email, @[team:TEAM-ID] mentions a GP team (expanded to its members). Any @[…] in the body is treated as a mention token, so if you need the literal characters @[ in your text, escape them as @\[. A token that does not resolve to a thread-visible member (unknown email, a non-member, a user outside the thread's visibility tier, an unknown team) is kept as its literal token text (@[[email protected]]) — the same in body and bodyHtml — the request is never rejected for an unresolvable mention, and no mention or notification is recorded for it. A resolved mention always shows the member's current name; a Label you send in bodyHtml is not stored.
Formatting. Send each comment as either body or bodyHtml — not both, and not neither (400).
bodyis plain text. Each line becomes a paragraph; a blank line is kept as one empty line. A line that starts with-or*becomes a bulleted-list item, and one that starts with a 1–3 digit number and.(e.g.1.) a numbered-list item; consecutive such lines form one list (numbering always restarts at 1). The marker must be at the very start of the line and be followed by text. To keep such a line literal, prefix it with a backslash:\- not a list. Any HTML-looking text inbodyis kept as literal text, never interpreted.bodyHtmlis HTML limited to<p> <br> <strong> <em> <u> <s> <ul> <ol> <li>plus mentions written as<span data-mention="@[[email protected]]">Label</span>(or@[team:TEAM-ID]). Lists cannot be nested. Any other element or attribute — links,style,class, images — is rejected with400naming it; nothing is silently dropped. Whitespace between tags is ignored (only<br>breaks a line). ThebodyHtmlreturned by ListThreadComments / ExportFundComments is accepted here as-is.
Notifications. notifyMode (default none) controls whether an import notifies the thread's audience. none is fully silent — no in-app notifications and no emails — recommended for historical migrations so a bulk backfill never storms members. inApp records the in-app unread rows (the thread lights for its thread-visible members) but sends no email digest. all sends both in-app and email. Mentions in the body are always parsed and stored, but a mentioned member is notified only when notifyMode is inApp or all.
Retries. Comment ids are system-generated: the response's commentIds (in input order) are the only handle on what was stored. Import is not idempotent — re-sending a request (or an already-imported comment) appends new comments rather than overwriting, so a blind retry after an ambiguous failure can duplicate. Before retrying, read the thread back (ListThreadComments) or correlate via your own externalRefs to remove the comments that already landed.
Imported metadata. The request has no createdAt field — an imported comment's createdAt is server-assigned at import time (in array order) and read back in (createdAt, commentId) order. Imported comments carry an importedMetadata object on export. It echoes onBehalfOf and externalRef verbatim when they were supplied; each field is absent otherwise. The presence of importedMetadata is what marks a comment as imported. externalRef is an optional correlation tag for your own systems — not a de-duplication key; it is echoed back on export but never affects storage.
Resolved threads. A thread whose status is resolved accepts no new comments: the import is rejected with 409 THREAD_RESOLVED and nothing is written. This matches the app, where the reply box is hidden on a resolved thread. There is no public endpoint to reopen a thread — reopen it in the app, then re-send the import. Check status in ListCommentThreads before importing if you need to avoid the round trip. The check runs after the permission checks, so a caller without access to the thread gets 403 and never learns its status.
Limits. 1–100 comments per request; each comment at most 10,000 visible characters (formatting and mention markup do not count; a mention counts as its label), with the stored HTML at most 64 KB; at most 200 comments per thread. Mentions: each comment may mention at most 50 distinct people or teams (a team counts once) and hold at most 200 mention tokens in total; one request may mention at most 500 distinct email addresses. Unresolvable tokens count toward these limits. A request over a mention limit is rejected with 400 IMPORT_VALIDATION_FAILED naming the comment, and nothing is written. The service account needs permission to post comments at the thread's visibility tier (403 otherwise); an unknown or foreign threadId is 404; a resolved thread is 409.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||