Skip to main content
POST
Beta. The direct upload flow is in active development. The request and response shapes shown here are stable for production use, but we may add new fields or capabilities without notice.
Use this to ship a new version of a file without re-wiring anything. The asset keeps its ID and stays attached to every digital product and order it was already linked to, so buyers downloading it receive the new file automatically — there is no need to create a fresh asset and re-attach it. Only internal assets can be replaced. The flow mirrors creating an internal asset: the response includes a single presigned PUT URL — upload the new file body to that URL to finish. Once the replacement is committed, the previous file is removed and any watermarking is re-applied to the new body. Plan storage quota is enforced on the growth in size (new byte_size minus the current size); the per-file ceiling is 2 GB.

Path parameters

string
required
The ID (UUID) of the internal asset to replace.

Request body

object
required

Response

object
required
The asset, with its ID unchanged.
object
required
A single-PUT handle (method: "PUT") with the presigned URL and headers required to upload the new file body. See Upload Asset for the field-by-field breakdown.