Read a drive item
GEThttps://
Returns one drive item in the detail view.
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.
- 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
access is the calling user's own effective access level on it. The body is not here: read content_record_id and GET /api/v2/drive-documents/{drive_document} for it. owner, drive_folder and tags render as references until named in include; an organisation-owned item's owner is always a bare reference. An archived item is 404 unless trashed=with is passed, and trashed=only 404s a live one. The declared permission is project_drive::access; the other three drive prefixes apply by owner type, and the per-item rule is what actually decides.
Path parameters
Query parameters
Unknown parameters are refused with 400, naming the parameter.
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 DriveItem in the detail view.
Headers
ETag- A strong validator of exactly this representation.
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
What this item is. Everything created through the API is a document; the other kinds come from uploads in plnnrly.
documentpdfimageaudiovideoofficeother
New values may be added.
Where the item came from: builtin for an editor document, upload for a file uploaded in plnnrly.
builtinupload
New values may be added.
The folder this item sits in; absent for items at the drive root.
The kind of record owner points at; it says which branch of owner applies.
projectcustomerorganizationuser
New values may be added.
The project, customer, organisation or user whose drive this item lives in. An organisation-owned item renders as a bare {"id": N} reference.
Which form you get depends on owner_type.
projectProjectSummarycustomerCustomerSummaryorganizationRefuserUserSummary
The kind of record content_record points at; it says which branch of content_record applies.
drive_document
New values may be added.
The body this item points at: a drive document for an editor document, null for an item with no body yet. Renders as a bare {"id": N} reference; read the body from GET /api/v2/drive-documents/{drive_document}.
Which form you get depends on content_record_type.
drive_documentRef
Sort position, assigned by the server. Positions count per drive and folder, so the sequence is only meaningful once the collection is narrowed to one drive and one folder. Reordering is not exposed in v2.0.
Author; always the authenticated user at create time. Null on legacy rows and where the author has since been deleted.
The user who archived this item; set on delete and cleared on restore.
Baseline sharing tier, consulted only while inherits_permissions is false.
everyone_editeveryone_viewrestricted
New values may be added.
The calling user's effective access level on this item, after the permission for the owner type, the access inherited from folders and any per-item grant.
viewedit
New values may be added.
When this item was archived, or null while it is live.
Files attached to this item, counting the attachments list in plnnrly, the single uploaded file and the images embedded in the document body.
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, PATCH, DELETE. Anything else answers 405.
Something wrong or missing on this page? Tell us