Complete Video Upload
POST/api/videos/:video/complete
Finish a multipart upload started with Start Video Upload after every part was PUT. The server joins the parts and queues the video check; the video moves to processing, then ready or failed.
tiktok-posts:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
parts ([{n, etag}], optional, up to 10000 entries; n is the 1-based part number, etag is optional) is accepted for compatibility but not needed — the server reads the stored parts itself. Completing an already-completed upload returns the video unchanged.
Returns 422 with the missing part numbers when parts are still missing (the upload stays open), when the upload is no longer open, or when another request is finishing the same upload right now. Every part but the last must be exactly part_size bytes and the parts must add up to the size given at start; otherwise the upload is discarded, the video is marked failed and 422 explains which part is wrong.
Authentication: Requires Bearer token (scope tiktok-posts:write). Permission: products.update or tiktok_posts.create.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.