{
"upload_session_id": 123
}
{
"status": "success",
"data": {
"id": 502,
"parent_id": 22,
"is_root": false,
"item_type": "file",
"name": "Annual report.pdf",
"file_size": 12345,
"content_type": "application/pdf",
"content_version": 0,
"createdby": 7,
"createddate": "2026-10-24T10:05:00Z",
"lastmodifieddate": null
}
}
Drive
Commit a Drive Upload
Validate an uploaded file and make it available in Drive.
POST
/
v1
/
drive
/
files
/
commit
{
"upload_session_id": 123
}
{
"status": "success",
"data": {
"id": 502,
"parent_id": 22,
"is_root": false,
"item_type": "file",
"name": "Annual report.pdf",
"file_size": 12345,
"content_type": "application/pdf",
"content_version": 0,
"createdby": 7,
"createddate": "2026-10-24T10:05:00Z",
"lastmodifieddate": null
}
}
After starting an upload and putting the bytes at its temporary URL, commit the session to create the Drive file.
Required scope:
Use the original API key. The session must belong to the key owner and the resolved chapter. Association-wide keys must specify the original
The file now appears in Drive. The response includes metadata; use its
A session can be committed once. After an uncertain response, check List Drive Items before starting another upload; listing requires
drive:write
This endpoint requires the Drive document creation API to be deployed to the selected environment, with Drive enabled.
chapter_id again.
The API rechecks current folder permissions, the file’s exact size, its signature and available storage quota. On success, it creates the file with inherited permissions and records the upload in the chapter’s activity log.
{
"upload_session_id": 123
}
{
"status": "success",
"data": {
"id": 502,
"parent_id": 22,
"is_root": false,
"item_type": "file",
"name": "Annual report.pdf",
"file_size": 12345,
"content_type": "application/pdf",
"content_version": 0,
"createdby": 7,
"createddate": "2026-10-24T10:05:00Z",
"lastmodifieddate": null
}
}
id with Download a Drive File to fetch it with drive:download.
| Status | Meaning |
|---|---|
400 | Missing uploaded bytes, size mismatch, invalid signature or quota exceeded |
403 | Missing scope, forbidden chapter or insufficient current Drive permissions |
404 | Session unavailable, including one owned by someone else or in another chapter |
409 | Session already finalized, or a file with this name already exists |
410 | Session expired; start a new upload |
503 | Drive is disabled |
drive:read.Authorizations
ApiKeyAuthBearerAuth
Query Parameters
Required for association-wide keys; must match the key's chapter for chapter-bound keys.
Body
application/json