Uploads

Retrieve an upload

Returns the current state of an upload. On the first call after the client has PUT bytes to the presigned URL, ShortSync finalizes the upload: it reads the stored Content-Type, validates it against the MIME allow-list, checks per-kind size caps and workspace storage quota, and marks the upload ready. Polling before the PUT is cheap — calls just return status: "reserved" with no side effects.

If the stored Content-Type isn't supported, the server deletes the S3 object and responds 415 UNSUPPORTED_FILE_TYPE. Reserve a new upload_id and retry with a correct Content-Type on the PUT.

get/uploads/{upload_id}

Request

  • Base URL: https://api.shortsync.app/v1
  • URL: https://api.shortsync.app/v1/uploads/{upload_id}
  • Auth: HTTP bearer

Response

Upload.

idstring required
status'reserved' | 'ready' required
  • reserved - ticket issued, bytes not yet finalized
  • ready - bytes finalized, usable as a post source

In v1 the server skips the post-upload media probe, so transitional uploaded / failed states are reserved for future use.

filenamestring required

Original filename if supplied to POST /uploads; otherwise derived from the S3 object key (typically the literal "upload" for empty-body reservations).

content_typestring required

Canonical MIME of the uploaded bytes (e.g., video/mp4, image/jpeg), read from the Content-Type the client set on the PUT to the presigned URL and validated against the allow-list at finalize.

size_bytesinteger required
workspace_idstring required
created_atstring date-time required
updated_atstring date-time

Changes

No recorded changes to this operation across all 1 revision of this API.