hosting
PUT /v1/sites/{siteId}/files/content
Replace or create one text file of the site.
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
| Name | Type | Required | What it is |
|---|---|---|---|
siteId (path) | Uuid | Yes | Site ID (UUIDv7). |
Request body
| Name | Type | Required | What it is |
|---|---|---|---|
path | string | Yes | — |
content | string | Yes | The whole new content, UTF-8. |
expected_sha256 | string | No | The sha256 the file had when read. |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
ok | boolean | Yes | — |
error | string | No | — |
path | string | No | — |
entries | object[] | No | — |
truncated | boolean | No | — |
content | string | No | — |
bytes | integer | No | — |
sha256 | string | No | — |
backup | string | No | Where the previous file was copied |
Errors this endpoint can return
401 · 403 · 404 · 422 · 503