marketplace
GET /v1/marketplace/overview
The marketplace hub — every vertical, the latest Zinn®s, what recently sold.
Authentication
This endpoint takes no API key. Anything else it needs, such as a signed request, is described above.
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 GET https://api.zinndigital.com/v1/marketplace/overview \
-H "Authorization: Bearer zdk_live_…"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/83 §6's hub, and the front door of the storefront. Anonymous, single-variant, no user-agent branch: these pages exist to rank, and a hub behind auth is a hub no crawler and no first-time visitor ever sees. Each vertical declares its own storefront_layout, which is what makes "layouts suited to what is sold" (owner, 2026-08-08) a row an operator can change rather than a map compiled into the frontend — a guest post renders as a comparison row, a website as a showcase, and the ninth marketplace is data entry rather than a deploy. ⛔ recently_sold respects the mask: a sold website's domain stays site****.com exactly as a live listing's does. Selling a site does not make its domain public.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
locale (query) | string | No | Explicit, never Accept-Language. A response that varied on a request header would need Vary, at which point the edge can serve a crawler a different page from the one a… |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
verticals | MarketplaceHubVertical[] | Yes | — |
latest | MarketplaceHubCard[] | Yes | — |
recently_sold | MarketplaceRecentSale[] | Yes | — |
total_listings | integer | Yes | — |