identity

GET /v1/me/overview-shortcuts

Get this person's Overview shortcut cards.

所有 identity 端点

所有开发者文档

身份验证

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

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

免费试用

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

curl -X GET https://api.zinndigital.com/v1/me/overview-shortcuts \
  -H "Authorization: Bearer zdk_live_…"

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

详细信息

The shortcut cards this person pinned to their dashboard Overview, in the order they appear. ⚖️ Owner, 2026-09-11: "on the overview screen we should have shortcuts to most-used sections, and the user should be able to select from all the sections and menu items to add their own shortcuts". ⛔ The ids are the dashboard's own navigation ids and are stored OPAQUELY. The section list is built per render from the caller's entitlements, permissions, brand and product lines — roughly 200 entries — so an allow-list in the engine would be correct on the day it was typed and would then start refusing nav entries shipped after it. The client resolves each id against the live tree it is already holding and drops what no longer exists. ⛔ Read chosen before rendering. An empty list with chosen: false means nobody has ever chosen and the client shows its presets; the identical list with chosen: true means this person deliberately removed every card, and the presets must NOT grow back.

响应

名称类型必填内容简介
shortcutsOverviewShortcutIdsDashboard navigation ids, in the order the cards appear. Opaque to the engine: it bounds the count, the length and the charset and stores the rest verbatim, because the section…
chosenbooleanWhether this person has ever chosen. ⛔ Not inferable from an empty list, which is why it is on the wire: false with an empty list means nobody has chosen and the client shows…

此端点可能返回的错误

401 · 403 · 429