hosting

PUT /v1/sites/{siteId}/files/content

Replace or create one text file of the site.

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 key must carry the sites.view permission; 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}/files/content \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "path": <string>, "content": <string> }'

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 current file is copied to .zinn-file-backups/ (denied to the web) first, then the new content is written atomically (temporary file + rename). With expected_sha256 the write is refused when the file changed since it was read. The audit row records the path, size and hashes — never the content. Requires sites.view and sites.panel_access. Fleet only.

Parameters

NameTypeRequiredWhat it is
siteId (path)UuidYesSite ID (UUIDv7).

Request body

NameTypeRequiredWhat it is
pathstringYes—
contentstringYesThe whole new content, UTF-8.
expected_sha256stringNoThe sha256 the file had when read.

Response

NameTypeRequiredWhat it is
okbooleanYes—
errorstringNo—
pathstringNo—
entriesobject[]No—
truncatedbooleanNo—
contentstringNo—
bytesintegerNo—
sha256stringNo—
backupstringNoWhere the previous file was copied

Errors this endpoint can return

401 · 403 · 404 · 422 · 503