Creative Hub
Multipart file upload
The 5-step flow for uploading a large file (video) in parts.
Use the multipart flow instead of the single-PUT Upload a file when the file is large (>~50 MB) — typically video. You upload the file to S3 in parts, then finalize.
The flow
- Start the upload —
POST /files/multipart. Returns afileIdand anuploadId. See Start a multipart file upload. - Sign the parts —
POST /files/multipart/{fileId}/parts/sign. Returns one pre-signedPUTURL per part number. You can request every part in one call. See Sign multipart parts. - Upload each part to S3 — for each part,
PUTthe chunk bytes directly to its signed URL (not through the Adnova API). Each part is 10 MB (10485760 bytes) except the last, which holds the remainder. Each signed URL enforces that part's exactContent-Length, so the bytes youPUTmust match. S3 returns the part'sETagin the response header; keep eachETagwith its part number. - Report the parts —
POST /files/multipart/{fileId}/parts/reportwith the{ partNumber, etag }list. Adnova stores the ETags server-side, so restarts and retries are safe. See Report multipart parts. - Complete the upload —
POST /files/multipart/{fileId}/complete. S3 assembles the parts in part-number order, Adnova writes theFilerow in the destination board, and the response returns theversionId. See Complete a multipart file upload.
Once complete, use the returned fileId as a creative _id in an Ad Launcher launch payload.
Notes
- Split the file into 10 MB parts (
10 * 1024 * 1024bytes); the last part holds the remainder. - Order doesn't matter for signing/uploading, but parts are assembled in ascending
partNumberorder at step 5. - Reporting is idempotent — re-reporting the same part with the same
ETagis safe, which makes resumable uploads straightforward. - All parts must be reported before calling
/complete. - Limits: the file is capped at 1 GB and must fit your plan's storage quota, or step 1 returns
413.
