GET /v1/marketplace/vendor/payouts

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/vendor/payouts \
  -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

⭐ This is what makes a HELD payout something a seller can act on rather than money that silently did not arrive. docs/82 §7a is explicit that an unverified vendor is told exactly why and what to do, and a hold with no surface is the same as no hold at all from where they are standing — they simply were not paid. `hold_reason` is a NAMED code rather than prose, so a console can render an instruction per reason: "finish your verification" is a different action from "your balance is below this rail's minimum and is rolling over to next week". `external_ref` is empty for account credit, which never leaves the platform — a real distinction rather than a missing value.

Cabiraha

Jawaab

Cilladaha ay bartaani soo celin karto

401