hosting
PUT /v1/sites/{siteId}/wordpress/uploads/{uploadId}/parts/{partNumber}
Send one part of a resumable upload.
Authentication
Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X PUT https://api.zinndigital.com/v1/sites/{siteId}/wordpress/uploads/{uploadId}/parts/{partNumber} \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
The raw bytes of one part, as application/octet-stream. Every part is exactly part_size bytes except the last, which is the remainder; any other length is refused 422. X-Zinn-Part-Sha256 carries the part's SHA-256 (hex). A part whose bytes do not match it is refused 422 and not stored, so the client sends that part again. Sending a part twice is safe: it replaces itself. 409 once the upload has been completed or has expired.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
siteId (path) | Uuid | Yes | Site ID (UUIDv7). |
uploadId (path) | string | Yes | A resumable upload's id, from startSiteWordPressUpload. |
partNumber (path) | integer | Yes | 1-based part number, up to the upload's part_count. |
X-Zinn-Part-Sha256 (header) | string | Yes | Lower-case hex SHA-256 of this part's bytes. |
Errors this endpoint can return
401 · 403 · 404 · 409 · 422 · 429