board-github
POST /v1/board-github/links/{linkId}/sync
Refresh one connection from GitHub now.
身份验证
请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限，因此请为您的密钥赋予所需的最小权限，并通过检查响应来确认，而不是盲目假设。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X POST https://api.zinndigital.com/v1/board-github/links/{linkId}/sync \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
The Temporal sweep does this every five minutes and the webhook does it in seconds; this is the button for somebody who does not want to wait. Both cursors come back. `last_attempted_at` moves for every attempt and `last_synced_at` only on success — so *"last synced 4 minutes ago"* beside *"last attempted 10 seconds ago"* is how a customer sees that we are trying and GitHub is refusing. One timestamp cannot say that.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
linkId (path) | string | 是 | The GitHub Projects connection. |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
ok | boolean | 否 | A distinct field rather than something inferred from the counts. A project that legitimately has no items and a sync that could not see anything are the same zeros. |
error | string | 否 | — |
items_seen | integer | 否 | — |
items_created | integer | 否 | — |
items_updated | integer | 否 | — |
items_archived | integer | 否 | — |
fields_seen | integer | 否 | — |
conflicts | integer | 否 | — |
pushed_back | integer | 否 | Fields OUR value won and were therefore re-pushed to GitHub. Keeping a won value only on our side would be a resolution that resolves nothing and reports the same conflict on th… |
pages | integer | 否 | — |
last_synced_at | string | 否 | — |
last_attempted_at | string | 否 | — |
此端点可能返回的错误
401 · 403 · 404