List a drive item's comments
GEThttps://
Returns the comment thread on one drive item (the same thread the drive document editor writes), newest first, keyset-paginated.
Access
- Token scope
- api:
read: orapi:project_drive read: orapi:customer_drive read: orapi:organization_drive read: user_drive Without it:
403 insufficient-token-scope. - Permission
- project_drive::
access Without it:
403 insufficient-permission. - Rate cost
- 1 unit, read bucket.
view=detailmakes it 3. Adds:with_total=1+2, each include +1. - Also
If-None-Matchanswers304when nothing changed. Never cached:private, no-store. Unknown query parameters are refused, never ignored.
Both are checked, scope first. A token never does more than its user. How access is checked
There is no organisation-wide collection of comments, so this nested path is the only way to list them and filter[commentable_type] / filter[commentable_id] do not exist: the parent is the path segment. Access to the parent is decided per item (the permission for the owner type, the access inherited from its folder, then any per-item grant), and an archived drive item answers 404, because comments are hard-deleted and trashed is therefore not an accepted parameter on this path. The declared permission is project_drive::access; customer_drive, organization_drive and user_drive apply by owner type, and a token covering any of the four is accepted. Pass include=author to expand each comment's author; the body is in both views. One comment is read, edited and deleted at its flat path /comments/{comment}, listed under Work items.
Path parameters
Query parameters
Unknown parameters are refused with 400, naming the parameter.
15 parameters in 6 groups
Views
Pagination
Cursor pagination only. Follow links.next.
Rows per page. At most 25 when include names a to-many relation; a larger value is 400 invalid-query-parameter.
Default: 25
Filters
- =
- equals
- [gte][lt]
- at least, less than
Sorting
| Key | Sorts by |
|---|---|
created_at | When the comment was posted, newest first. |
id | Id, ascending. An id never changes, so use this for a stable full export. |
updated_at | Last-write timestamp; pair with the id tiebreaker for sync. |
Prefix a key with - for descending.
Includes
| Path | Adds | Cost |
|---|---|---|
author | Expand the author into a name-and-id object instead of a bare reference. | +1 |
Other
Request headers
A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.
Response 200
Returns a page of CommentList rows.
The rows, each a CommentList.
per_page, next_cursor, prev_cursor, total.
self, next, prev.
Each row is a CommentList: 11 fields.
Headers
ETag- A weak validator (
W/"…") of the rendered page. RateLimit- The IETF
httpapi-ratelimit-headersform of your remaining allowance on the tightest bucket this request touched. RateLimit-Policy- The ceiling and window of that bucket, as
<limit>;w=<seconds>. X-Request-Id- The server-generated ULID correlating this response with our logs.
Every response also carries Cache-Control, Vary, X-Content-Type-Options, X-Plnnrly-Api-Version, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. Headers and versioning
Comment body as rich text. HTML from the plnnrly editor, sanitised on the way out, so what you read back can differ from the bytes you sent. Mention spans (<span data-type="mention" data-id="3">) survive untouched and may be posted back verbatim; constructing a new mention is not supported in v2.0.
The kind of record commentable points at; it says which branch of commentable applies.
work_itemdrive_item
New values may be added.
The record the comment hangs off, as a reference. Look it up from commentable_type and commentable_id with GET /api/v2/work-items/{id} or GET /api/v2/drive-items/{id}. It is not expandable: ?include=commentable is a 400.
Which form you get depends on commentable_type.
work_itemRefdrive_itemRef
Last-write timestamp; use for incremental sync, and as the revision the strong ETag is derived from.
Errors
8 errors every operation can return: 304, 400, 401, 404, 406, 429, 500, 503
304 Not modified.
400 Bad request.
idempotency-key-requiredinvalid-cursorinvalid-query-parametermalformed-requestunsupported-parameter
401 Unauthenticated.
404 Not found.
406 Not acceptable.
429 Too many requests.
500 Server error.
503 Service unavailable.
This path allows GET, POST. Anything else answers 405.
Something wrong or missing on this page? Tell us