List notes
GEThttps://
Returns the notes whose parent record the caller may read, oldest position first.
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
A note is visible exactly when the record it hangs off is: only notes on projects, customers and work items you can see are listed, so this collection can be read across the whole organisation without leaking a record the caller cannot open. Scope it to one record with the notable_type/notable_id pair, which must be sent together. total is omitted unless you pass with_total=1. The declared permission is project_drive::access; the other three drive prefixes (customer_drive, organization_drive, user_drive) apply by owner type, and a token covering any of the four is accepted.
Query parameters
Unknown parameters are refused with 400, naming the parameter.
18 parameters in 5 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
- [in]
- any of a comma-separated list
- [null]
trueorfalse: whether it is empty- [gte][lt]
- at least, less than
Creation timestamp. Pair with sort=id for a stable full export.
Id of the record the note is attached to, within the notable_type given. Must be sent together with notable_type.
A comma-separated list of at most 100 values.
Type of record the note is attached to: project, customer or work_item. Must be sent together with notable_id.
Last-write timestamp. Use for incremental sync.
Sorting
| Key | Sorts by |
|---|---|
order_column | Sort position within the parent record, ascending. |
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 |
|---|---|---|
notable | The project, customer or work item the note is attached to. | +1 |
user | The user who wrote the note. | +1 |
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 NoteList rows.
The rows, each a NoteList.
per_page, next_cursor, prev_cursor, total.
self, next, prev.
Each row is a NoteList: 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
Sort position within the parent record. Assigned by the server; reordering is not exposed in v2.0. Positions are not counted per parent, so the sequence is effectively creation order across the whole organisation.
Author of the note. Always the authenticated user at create time; null where the author has since been deleted.
The kind of record notable points at; it says which branch of notable applies.
projectcustomerwork_item
New values may be added.
The project, customer or work item this note is attached to.
Which form you get depends on notable_type.
projectProjectSummarycustomerCustomerSummarywork_itemWorkItemSummary
Author of the note.
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