Upload registration and URL expiry

Uploading bytes and registering the resulting object are distinct operations. Quota checks, registration retries and temporary URL expiry have separate effects.

Upload acceptance and registration retries

The size check uses currently reported quota and does not reserve storage for this upload. If the request is rejected for quota, let the customer remove unneeded files before trying again; see making room for another attachment. Several parallel uploads can consume the remaining space.

Show upload progress in your application, then check that the transfer succeeded. The size-range header permits anything from zero bytes to the declared maximum; it does not confirm that the complete intended recording arrived. Keep the URL private: it can permit another upload until it expires.

If registration's response is lost, retry registration for the same uploaded file. It returns the existing registration with an omitted/default registered flag when the file was already registered. Do not start another upload just because the registration response did not arrive.

File references and expiry

Upload and single-file download URLs default to one hour when expiry is omitted; batch download URLs default to 24 hours. Choose an expiry suitable for the current interaction rather than storing those links in your support-request record.