List a work item's attachments
GEThttps://
Returns the files attached to one work item, newest upload first, keyset-paginated.
Access
- Token scope
- api:
read: project_management Without it:
403 insufficient-token-scope. - Permission
- project_management::
view_backlog Without it:
403 insufficient-permission. - Rate cost
- 1 unit, read bucket.
view=detailmakes it 3. Adds: each include +1,q+2. - 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 files (a file is only ever reached inside its parent's collection), so this nested path is the only way to list a work item's attachments, and filter[model_type] / filter[model_id] do not exist: the parent is the path segment. The path takes the work item's numeric id or its issue key, so work-items/ACM-123/attachments and work-items/41/attachments are the same list. Work items are hard-deleted, so trashed is not an accepted parameter here. Listing additionally requires project_management::manage_work_items on the parent work item. The API never streams bytes: pass include=url for a signed download URL per file, and attach a new file with the two-step upload flow that starts at POST work-items/{work_item}/uploads.
Path parameters
Query parameters
Unknown parameters are refused with 400, naming the parameter.
15 parameters in 6 groups
Views
Pagination
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
Narrow to one media collection. A work item registers only attachments; a drive item registers attachments, content (inline editor images) and file (the single uploaded payload), so filter[collection]=file is how a client asks a drive item for its payload alone.
Creation timestamp. Pair with sort=id for a stable full export.
Last-write timestamp. Use for incremental sync.
Narrow to one media collection. A work item registers only attachments; a drive item registers attachments, content (inline editor images) and file (the single uploaded payload), so filter[collection]=file is how a client asks a drive item for its payload alone. One value, matched literally as a prefix: send commas and backslashes as they are, and % and _ match themselves rather than acting as wildcards.
Search
Sorting
| Key | Sorts by |
|---|---|
created_at | Upload timestamp, newest first. |
name | File name, A→Z. |
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 |
|---|---|---|
url | Signed download URL. Null where your organisation's file storage cannot sign URLs, with a signed_url_unavailable warning. | +1 |
url_expires_at | When the signed url stops working. Always null in v2.0: the signed URL does not expire. Request together with url. | +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 MediaList rows.
The rows, each a MediaList.
per_page, next_cursor, prev_cursor, total, current_page, last_page.
self, next, prev.
Each row is a MediaList: 10 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
Signed download URL, requiring your bearer token. Request with ?include=url. Null only where your organisation's file storage cannot sign URLs, in which case the response carries a signed_url_unavailable warning and downloads are not available through the API.
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