marketplace

PUT `/v1/marketplace/vendor/verification`

Open the identity file on a track, or edit it.

المصادقة

أرسل مفتاح واجهة برمجة التطبيقات (API) كرمز حامل (bearer token). لا يحدد نقطة النهاية هذه إذنًا محددًا في المواصفات، لذا امنح مفتاحك الحد الأدنى الذي محتاجه وتحقق من الاستجابة بدلاً من الافتراض.

لا يقبل هذا الطرف أي معرف للمؤسسة. يحدد مفتاحك بالفعل المؤسسة التي ينتمي إليها، وتكون الاستجابة محصورة في نطاقها.

جربه الآن

استبدل أي شيء بين أقواس زاوية بقيمك الخاصة، والعنصر النائب للمفتاح بمفتاح من لوحة تحكمك.

curl -X PUT https://api.zinndigital.com/v1/marketplace/vendor/verification \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "track": <MarketplaceVerificationTrack>, "legal_name": <string> }'

هل سجلت الدخول؟ تقوم وحدة تحكم واجهة برمجة التطبيقات في لوحة التحكم الخاصة بك بربط معرف مؤسستك الحقيقي ومفتاحك الخاص، وتنفذ الطلب مقابل واجهة برمجة التطبيقات المباشرة لتتمكن من رؤية الاستجابة الفعلية. افتح هذه النهاية الطرفية في وحدة تحكم API

التفاصيل

docs/82 §7a. **Two tracks, chosen here: individual and company.** They are not the same shape with extra fields — the required documents differ, the number of natural persons differs (one, versus every beneficial owner over 25%), and the approval rule differs, because a company is not verified until every required owner is. ⛔ `PUT`, not `POST`: there is exactly one file per seller and sending the form twice must not make two. ⛔ Refused once the file is in review or approved — the reviewer approves what they saw.

جسم الطلب

الاسم	النوع	مطلوب	ما هو هذا
`track`	`MarketplaceVerificationTrack`	نعم	Which set of rules the identity file is judged against (docs/82 §7a). The company track is not the individual track with extra fields: the required documents, the number of natu…
`legal_name`	`string`	نعم	The name exactly as it appears on the documents — a person's on the individual track, the company's on the company track. Not the storefront name: a storefront name is chosen an…
`country`	`string`	لا	ISO-3166-1 alpha-2.
`company_number`	`string`	لا	—
`registered_address`	`string`	لا	—
`tin`	`string`	لا	The seller's Tax Identification Number (docs/298 §2). For a UK company this is the CRN; for a UK individual their National Insurance number; elsewhere the local TIN. ⛔ R…
`tin_issued_in`	`string`	لا	ISO-3166-1 alpha-2 jurisdiction that ISSUED the TIN. ⛔ Not the same as `country`: a person resident in Ireland can hold a UK NI number, and reporting the residence country as th…
`tin_unavailable_reason`	`string<jurisdiction_does_not_issue, jurisdiction_does_not_require>`	لا	Why there is no TIN, where there legitimately is none. ⛔ There is deliberately no "seller refused" value — that is not a reason a TIN is unavailable, it is the reason the payout…
`residential_address`	`string`	لا	The individual seller's primary residence, as DAC7 asks for it. Individual track only — on the company track the primary address is `registered_address`, and a second column wou…
`accept_self_billing`	`boolean`	لا	Accept the self-billing agreement (docs/82 §8). Recorded with a timestamp and never cleared; required before the file can be submitted. Refused while `self_billing_vat_status` i…
`self_billing_vat_status`	`string<unknown, registered, not_registered>`	لا	Whether you are VAT registered. `not_registered` is a perfectly ordinary answer and self-bills correctly with no number on the document; what we cannot do is proceed without an…
`self_billing_vat_number`	`string`	لا	Your VAT registration number. Required when `self_billing_vat_status` is `registered`: an invoice we raise in your name must show it, or neither of us can account for the tax on…

الاستجابة

الاسم	النوع	مطلوب	ما هو هذا
`verification`	`MarketplaceVerification`	نعم	—
`requirements`	`MarketplaceVerificationRequirements`	نعم	What the file still needs, computed from the track. ⭐ Published so a screen renders the checklist rather than re-implementing the track rules and drifting from them.

الأخطاء التي يمكن أن تُرجعها نقطة النهاية هذه

401 · 404 · 422

PUT /v1/marketplace/vendor/verification