Document POST .../items/{item-id}/createUploadSession - #56
Open
dschmidt wants to merge 1 commit into
Open
Conversation
dschmidt
marked this pull request as ready for review
August 5, 2026 11:19
dschmidt
requested review from
butonic,
dragotin,
fschade,
kulmann,
micbar and
rhafer
as code owners
August 5, 2026 11:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents
POST /v1.0/drives/{drive-id}/items/{item-id}/createUploadSession(CreateUploadSession), which the OpenCloud graph service already serves but the spec never documented. Modeled on the MS Graph createUploadSession endpoint.The request body (
deferCommit,item.name,item.fileSize) reflects the fields the server actually honors; other MS GraphdriveItemUploadablePropertiesare ignored.For discussion: the 200 response deviates from MS Graph
The documented response reflects what the server returns today (verified live against a running instance), which is not MS-Graph-shaped:
UploadURL(capitalized), notuploadUrlCS3Protocolsarray (protocol/upload_endpoint/token/available_checksums) instead of MS Graph'sexpirationDateTime/nextExpectedRangesDocumented as-is. Open question for reviewers: should the server be aligned to the MS Graph
uploadSessionshape and the spec follow that, or is documenting the current CS3 shape the right call?