Skip to main content

Register a file uploaded via pre-signed URL

POST 

/api/v1/storage/register-uploaded-file

Step 3: after uploading, register the fileId with the same folderPath and intended fileName. The backend checks the object at the derived caller-scoped path and reads its stored size and content-type metadata. MIME metadata can be supplied by the uploader and is not byte/content validation. The signed-upload path does not compute a checksum.

An already registered fileId returns the existing record with registered false, which may be omitted. This retry behavior does not prove that a reused signed URL cannot subsequently alter the object. Missing uploaded objects return 404; quota and backend failures require reconciliation.

Request​

Responses​

File registered (or already registered)

Document ID: DOC-CP-files-data-api-registerUploadedFile. Section identities and revisions.

SectionStable reference
OverviewDOC-CP-files-data-api-registerUploadedFile#overview
RequestDOC-CP-files-data-api-registerUploadedFile#request
ResponsesDOC-CP-files-data-api-registerUploadedFile#responses