GET /v1/visibility/targets/{targetId}/backlink-links

身份验证

请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限，因此请为您的密钥赋予所需的最小权限，并通过检查响应来确认，而不是盲目假设。

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

免费试用

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

curl -X GET https://api.zinndigital.com/v1/visibility/targets/{targetId}/backlink-links \
  -H "Authorization: Bearer zdk_live_…"

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

详细信息

The per-link table behind the backlink counts: which page links to you, with what anchor text, how strong that page and its domain are, and whether the link is new, lost or broken. The aggregate profile answers *how many*; this answers *which*. Included with the backlink monitoring the plan already carries — there is no separate add-on to buy. `403` when the plan does not include backlink monitoring, and also when the account is not in good standing, because this endpoint spends money with the data provider at the moment it is called rather than reading a stored row. The page size is **not** a query parameter. It is derived in the adapter from the provider's measured price table, because it is a spend decision rather than a display preference: the provider charges a fixed fee per request plus a much smaller amount per row returned, so one large page costs barely more than one small page and paginating in small steps pays the fixed fee every time. `total` and `showing` are both returned and they are different facts. A response carrying only the list reads as complete however few rows it holds, so a caller that cannot say "showing 100 of 40,000" would present a page as the whole profile. Every rank and score is nullable. `null` means the provider gave no reading; `0` means it measured one and it is zero. A missing reading rendered as `0` makes a whole column of links look worthless when they are merely unmeasured.

参数

响应

此端点可能返回的错误

401 · 403 · 404 · 422