marketplace

POST `/v1/marketplace/vendor/profile`

Become a Zinner®.

身份验证

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

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

免费试用

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

curl -X POST https://api.zinndigital.com/v1/marketplace/vendor/profile \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "display_name": <string> }'

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

详细信息

docs/82 §7a. Self-service registration — until M1 a vendor row could only be created by staff in admin, which is a marketplace whose seller half is reachable only by asking us. ⭐ **Idempotent.** An org that is already registered gets `200` and its existing row, never a `409`: two members of one org pressing the button is an ordinary event. ⛔ The organization comes from the caller's own scope, never from the body — a caller-supplied org id would let a member of one tenant enrol another. ⛔ The row is always created `registered` and never first-party: registering is not approval, and approval is not verification.

请求正文

名称	类型	必填	内容简介
`display_name`	`string`	是	The name buyers see. Required.
`contact_email`	`string`	否	—
`country`	`string`	否	ISO-3166-1 alpha-2.

响应

名称	类型	必填	内容简介
`registered`	`boolean`	是	`false` is a normal answer — most customers are not sellers — and the other two fields are then `null`.
`vendor`	`MarketplaceVendorSelf`	是	—
`verification`	`MarketplaceVerification`	是	—

此端点可能返回的错误

401 · 422

POST /v1/marketplace/vendor/profile