billing
GET /v1/billing/adhoc-charges
The manual charges on your account, and what you have been billed.
身份验证
请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 billing.view 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。
您的组织 ID 应填在此处
此端点将 org_id 作为查询参数。不填则调用涵盖您的整个租户子树；发送该参数则将调用范围缩小到一个组织。
您的组织ID位于控制面板的API密钥屏幕上，就在密钥本身的旁边。这是您在每次调用时使用的相同ID。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/billing/adhoc-charges \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
Ad-hoc items on your own account — anything a member of our team added by hand — plus the history of what has actually been billed. Requires `billing.view`. Two questions, two halves: `data` answers *"is this going to happen again"* and `occurrences` answers *"which invoice was that line on"*. The staff notes that sit beside these items are never returned here. `occurrences[].paid` is tri-state: `true`, `false`, or `null` when the order could not be read — "we do not know" and "you have not paid" are different things to say to somebody about their own money.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
org_id (query) | string | 否 | Required when you belong to more than one organisation. Omitted, it means your own — which is ambiguous for a reseller or an agency, so that answers 422 rather than guessing. |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
data | AdhocCharge[] | 是 | — |
occurrences | AdhocChargeOccurrence[] | 是 | — |
此端点可能返回的错误
401 · 403 · 422 · 429