marketplace

POST /v1/marketplace/listings

Start a Zinn®.

All marketplace endpoints

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/listings \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "listing_type_id": <string>, "title": <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

Creates a draft. The listing type's CURRENT schema version is stamped onto it here, once, and never moved — tightening the type's schema later must not retroactively invalidate what was authored under the old one (docs/78 §4.2 trap 2). ⛔ The Zinner® must be `approved`. docs/78 §3.2 makes `under_review` the anti-fraud gate rather than a formality, and an account that can author listings while under review has walked straight through it.

Request body

NameTypeRequiredWhat it is
listing_type_idstringYes
category_idstringNo
titlestringYes
summarystringNo

Response

NameTypeRequiredWhat it is
idstringYes
vendor_idstringYes
marketplace_idstringYes
marketplace_keystringYes
category_idstringNo
listing_type_idstringYes
listing_type_keystringYes
schema_versionintegerYesThe version this listing's values were authored against. Stamped once, never moved — a later schema must not reinterpret an older listing.
titlestringYes
slugstringYesPermanent once live. It is the public URL.
summarystringYes
field_valuesobjectYes"`{key: {v, ver}}`" — uniform two keys, `ver: null` for a seller-declared value, so no consumer branches on key presence. ⛔ A `domain` value is NOT here — it is in the reveal ta…
field_schemaMarketplaceFieldDefinition[]NoPresent on the detail read; the schema THIS listing is authored against.
stateMarketplaceListingStateYes⛔ `archived`, never deleted. A listing that sold has public URLs, backlinks and an order behind it, and a 404 costs rankings that do not come back.
price_minorintegerYes
price_max_minorintegerYes
currencystringYes
published_atstringNo
packagesMarketplacePackage[]Yes

Errors this endpoint can return

401 · 409 · 422