GET /v1/marketplace/overview

Xaqiijinta aqoonsiga

U dir fure API ahaan calaamad muujisa (bearer token). Barta dhammaadka ee kani ma caysino luqad ahaan oggolaansho gaar ah oo ku dhex jirta qeexidda, markaa sii furahaaga inta ugu yar ee uu u baahan yahay oo fiiri jawaabta halka aad wax ka qaadan lahayd.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

curl -X GET https://api.zinndigital.com/v1/marketplace/overview \
  -H "Authorization: Bearer zdk_live_…"

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Faahfaahin

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.

Cabiraha

Jawaab