hosting

POST /v1/connector/backup/claim

Ask whether a backup is due — called by the Zinn® WordPress connector plugin.

所有 hosting 端点

身份验证

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

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

免费试用

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

curl -X POST https://api.zinndigital.com/v1/connector/backup/claim \
  -H "Content-Type: application/json" \
  -d '{  }'

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

详细信息

**Unauthenticated by session, authorised by a per-site bearer token** minted when the customer connected the site. The caller is PHP on a server we have never seen and has no session with us. Returns either a job (`job_id` plus a short-lived presigned upload URL) or an empty object meaning *nothing due*. The plugin polls hourly and streams the archive straight to object storage, so it never passes through our servers. ⛔ **A wrong or unknown token returns `200` with an empty body, exactly like "nothing due".** That is deliberate and is the opposite of what an API normally does: a `401` would confirm to an unauthenticated caller that a given site is enrolled for backups, and this route is reachable by anyone. The plugin cannot tell the two apart either, and does not need to.

请求正文

名称类型必填内容简介
site_urlstringThe plugin's own view of the site address, for diagnostics only.

响应

名称类型必填内容简介
job_idstringThe backup row this upload settles.
upload_urlstringA short-lived presigned PUT. ⛔ A bearer credential — whoever holds it can write that object — so the plugin never logs it, stores it, or shows it in an admin notice. It grants e…

此端点可能返回的错误

429