Authentication
Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
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> }'Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
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.
Request body
| Name | Type | Required | What it is |
|---|---|---|---|
display_name | string | Yes | The name buyers see. Required. |
contact_email | string | No | — |
country | string | No | ISO-3166-1 alpha-2. |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
registered | boolean | Yes | `false` is a normal answer — most customers are not sellers — and the other two fields are then `null`. |
vendor | MarketplaceVendorSelf | Yes | — |
verification | MarketplaceVerification | Yes | — |
Errors this endpoint can return
401 · 422