agency-invoicing
POST /v1/agency-invoicing/logo
Upload the logo your invoices carry.
身份验证
请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 agency.invoicing.manage 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。
您的组织 ID 应填在此处
此端点将 org_id 作为查询参数。不填则调用涵盖您的整个租户子树；发送该参数则将调用范围缩小到一个组织。
您的组织ID位于控制面板的API密钥屏幕上，就在密钥本身的旁边。这是您在每次调用时使用的相同ID。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X POST https://api.zinndigital.com/v1/agency-invoicing/logo \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
⛔ Its own door, and `POST /v1/branding/logo` cannot serve it: that one stores the mark for a white-labelled **panel**, demands `reseller.manage`, and refuses unless white-label is on the plan — with the message *"a logo here would appear nowhere"*. On a panel that is right. On an invoice it is false: the document is your own paper and carries your mark whatever your plan says. ⭐ The image is vetted and stored content-addressed; the digest returned is what the PDF inlines as a `data:` URI, which is what keeps the render offline. Requires `agency.invoicing.manage`.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
org_id (query) | Uuid | 否 | Which of your organizations is invoicing. Required only when you belong to more than one — otherwise it is inferred from your DIRECT membership, never from the subtree-expanded… |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
logo_sha256 | string | 是 | The content digest. ⛔ Not a URL — the invoice renderer inlines the bytes as a `data:` URI and follows no external reference at render time. |
width | integer | 否 | — |
height | integer | 否 | — |
byte_size | integer | 否 | — |
此端点可能返回的错误
401 · 403 · 404 · 422 · 429