hosting

POST `/v1/connector/backup/complete`

Report a finished backup — called by the Zinn® WordPress connector plugin.

身份验证

此端点是公开的。它不需要任何凭据或组织——这是我们自己的营销网站和 AI 问答引擎所读取的内容。

此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。

免费试用

将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。

curl -X POST https://api.zinndigital.com/v1/connector/backup/complete \
  -H "Content-Type: application/json" \
  -d '{ "job_id": <string>, "status": <string<uploaded, failed>> }'

已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。在 API 控制台中打开此端点

详细信息

Settles the job the plugin claimed. Same bearer token, same silent treatment of an unknown one. ⛔ **The reported `size_bytes` is a cross-check, not the record.** We HEAD the stored object ourselves, because a truncated upload that reports success is indistinguishable from a good one until somebody tries to restore it — and because a site could otherwise report `uploaded` having written nothing, leaving a restore button over an object that does not exist. A `failed` report settles the row so it is not left running for ever. The detail is kept for staff and never shown to the customer: it is untranslated English and can carry a filesystem path from their server.

请求正文

名称	类型	必填	内容简介
`job_id`	`string`	是	—
`status`	`string<uploaded, failed>`	是	—
`size_bytes`	`integer`	否	The plugin's own figure. A cross-check only — the recorded size comes from HEAD-ing the stored object.
`detail`	`string`	否	Why it failed. Kept for staff and never rendered to the customer: untranslated English that can carry a path from their server.

此端点可能返回的错误

422 · 429