CreateUploadSessionInput

A unique identifier for the client performing the mutation.

True when this grant is the client asking again after a failed attempt, rather than a fresh user action. An automatic retry and a new upload are otherwise identical requests, so without this a duplicate grant cannot be told from a first one in aggregate.

MIME type of the source file; stored in placeholder asset metadata

How many part uploads this client can keep in flight. Omit it (or send 1) and the session is planned for sequential upload, which is what every client that does not implement concurrency should do. Declaring more than 1 lets the server grant a wider max_parallel; it does not oblige the client to use the full width it is granted, and it does not change the part size.

Part size this client would like, in bytes. Honored by the direct-presigned strategy, clamped to a range whose floor is the shared default — so a client can ask for larger parts than the default but never smaller. Larger parts mean fewer requests and a costlier retry, since a failed part is re-uploaded whole. Omit it to get the shared default. The server-mediated strategy ignores it.

Advisory. Must match the asset_kind's bound strategy or the manager rejects.

The asset from the attempt this grant replaces, so the two grants can be joined. Telemetry only — it grants no access to that asset and is not validated against it.

ID of the space to upload into — resource ID or GlobalID.