board-github

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

One connection, with its WIP report and its open notices.

Све board-github крајње тачке

Сва документација за програмере →

Аутентификација

Пошаљите API кључ као bearer токен. Ова крајња тачка не наводи конкретну дозволу у спецификацији, па свом кључу доделите најмања неопходна овлашћења и проверите одговор уместо да претпостављате.

Ова крајња тачка не прихвата id организације. Ваш кључ већ идентификује организацију којој припада, а одговор је ограничен на њу.

Испробајте

Замените све што је у угластим заградама сопственим вредностима, а чувар места кључа кључем са своје контролне табле.

curl -X GET https://api.zinndigital.com/v1/board-github/links/{linkId} \
  -H "Authorization: Bearer zdk_live_…"

Пријављени сте? API конзола на вашој контролној табли попуњава ваш прави id организације и ваш сопствени кључ, и покреће захтев према живом API-ју како бисте могли да видите стварни одговор. Отворите ову крајњу тачку у API конзоли

Детаљи

The connection screen's whole payload in one call: the project, its fields with their options, the per-status counts against any WIP limits, and the notices GitHub does not raise — overdue items, items nothing has touched for a fortnight, and columns over their limit. last_synced_at and last_attempted_at are both returned and are different questions: a connection GitHub keeps refusing has a recent attempt and a stale success, and reporting only the first would show a healthy timestamp on a connection that has been broken for a week.

Параметри

НазивТипОбавезноШта је ово
linkId (path)stringДаThe GitHub Projects connection.

Одговор

НазивТипОбавезноШта је ово
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…
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 would…
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…
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…
wipGitHubProjectStatusCount[]Не—
noticesGitHubProjectNotice[]Не—

Грешке које ова крајња тачка може вратити

401 · 403 · 404