board-github

PATCH /v1/board-github/links/{linkId}

Change a connection's sync direction or the board it sits alongside.

همه نقاط پایانی board-github

احراز هویت

یک کلید API را به عنوان یک توکن برbearer ارسال کنید. این نقطه پایانی مجوز خاصی را در مشخصات خود ذکر نمی‌کند، بنابراین به جای فرض کردن، حداقل نیازهای کلید خود را بدهید و پاسخ را بررسی کنید.

این نقطه پایانی هیچ شناسه سازمانی را دریافت نمی‌کند. کلید شما در حال حاضر سازمان مربوطه را مشخص می‌کند و پاسخ در همان محدوده ارائه می‌شود.

امتحان کنید

هر چیزی را که داخل براکت‌های زاویه‌دار قرار دارد با مقادیر خودتان جایگزین کنید، و نگهدارنده کلید را با کلیدی از داشبورد خود جایگزین نمایید.

curl -X PATCH https://api.zinndigital.com/v1/board-github/links/{linkId} \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

وارد شده‌اید؟ کنسول API در داشبورد شما شناسه سازمان واقعی و کلید خودتان را پر می‌کند و درخواست را روی API زنده اجرا می‌کند تا بتوانید پاسخ واقعی را ببینید. این نقطه پایانی را در کنسول API باز کنید

جزئیات

`direction` moves a connection between two-way and read-only. A new connection is two-way immediately; read-only exists for a customer who wants a mirror they cannot break, and it is the honest remedy when GitHub keeps refusing our writes — turning writes off is better than a screen that accepts edits which never arrive.

پارامترها

نامنوعالزامیچیست
linkId (path)stringبلهThe GitHub Projects connection.

بدنه درخواست

نامنوعالزامیچیست
directionGitHubSyncDirectionخیر`both` is the default (owner ruling, 2026-09-03: a new connection is read-write immediately). `pull` is the honest remedy when a push keeps being refused.
notice_deliveryGitHubNoticeDeliveryخیرWhere a connection's overdue / gone-quiet / over-WIP notices are allowed to go. Both values raise the same notices and both render them on the board — the difference is delivery…
board_idstringخیر

پاسخ

نامنوعالزامیچیست
idstringخیر
board_idstringخیر
auth_kindGitHubAuthKindخیر`app` is the Zinn® GitHub App installation — per-repository scope the customer chooses on GitHub's own screen, revocable by them in one click, belonging to their organisation ra…
installation_idstringخیرPublic — it appears in the customer's own install URL — and showing it is what lets them confirm on GitHub that they are looking at the right installation.
has_stored_tokenbooleanخیرWhether a token is held in Vault for this connection. The token itself is never returned.
project_node_idstringخیر
project_numberintegerخیر
owner_loginstringخیر
owner_typestringخیر
titlestringخیر
short_descriptionstringخیر
closedbooleanخیر
publicbooleanخیر
directionGitHubSyncDirectionخیر`both` is the default (owner ruling, 2026-09-03: a new connection is read-write immediately). `pull` is the honest remedy when a push keeps being refused.
notice_deliveryGitHubNoticeDeliveryخیرWhere a connection's overdue / gone-quiet / over-WIP notices are allowed to go. Both values raise the same notices and both render them on the board — the difference is delivery…
viewsobject[]خیرThe project's saved views on GitHub, replaced whole on every read so a view deleted there disappears here rather than lingering as a link GitHub answers with a 404. Rendered as…
urlstringخیر
webhook_stateGitHubWebhookStateخیرWhether GitHub pushes changes at us, and if not, whose move it is. **Three outcomes and not a boolean.** `automatic` — we created the organisation webhook. `manual` — GitHub wou…
last_synced_atstringخیرWhen a sync last SUCCEEDED. What the staleness alarm fires off.
last_attempted_atstringخیرWhen a sync was last ATTEMPTED, stamped for every connection the sweep reaches before the result is read. Two columns rather than one: a cursor only a successful pass advanced w…
last_errorstringخیر
created_atstringخیر
fieldsGitHubProjectField[]خیرThe project's fields, with their single-select options and any work-in-progress limits set on them. Returned with the connection rather than fetched separately, because a board…

خطاهایی که این نقطه پایانی می‌تواند برگرداند

401 · 403 · 404 · 422