hosting

PUT /v1/sites/{siteId}/wordpress/uploads/{uploadId}/parts/{partNumber}

Send one part of a resumable upload.

All hosting endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The endpoint checks sites.panel_access, sites.view; a key without it is refused with 403, not 404.

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

NameTypeRequiredWhat it is
siteId (path)UuidYesSite ID (UUIDv7).
uploadId (path)stringYesA resumable upload's id, from startSiteWordPressUpload.
partNumber (path)integerYes1-based part number, up to the upload's part_count.
X-Zinn-Part-Sha256 (header)stringYesLower-case hex SHA-256 of this part's bytes.

Errors this endpoint can return

401 · 403 · 404 · 409 · 422 · 429