marketplace
GET /v1/marketplace/vendor/payouts
What has been paid out, and what is being held.
身份验证
请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限,因此请为您的密钥赋予所需的最小权限,并通过检查响应来确认,而不是盲目假设。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织,且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值,并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/marketplace/vendor/payouts \
-H "Authorization: Bearer zdk_live_…"已登录?您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥,并针对实时 API 运行请求,以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
⭐ This is what makes a HELD payout something a seller can act on rather than money that silently did not arrive. docs/82 §7a is explicit that an unverified vendor is told exactly why and what to do, and a hold with no surface is the same as no hold at all from where they are standing — they simply were not paid. `hold_reason` is a NAMED code rather than prose, so a console can render an instruction per reason: "finish your verification" is a different action from "your balance is below this rail's minimum and is rolling over to next week". `external_ref` is empty for account credit, which never leaves the platform — a real distinction rather than a missing value.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
cursor (query) | string | 否 | Opaque cursor from a previous page's `page.next_cursor`. |
limit (query) | integer | 否 | Maximum items to return (page size). |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
data | MarketplacePayout[] | 是 | — |
page | PageMeta | 是 | — |
此端点可能返回的错误
401