marketplace

PUT /v1/marketplace/vendor/verification

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

همه نقاط پایانی marketplace

همهٔ مستندات توسعه‌دهندگان

احراز هویت

یک کلید API را به عنوان یک توکن برbearer ارسال کنید. این نقطه پایانی مجوز خاصی را در مشخصات خود ذکر نمی‌کند، بنابراین به جای فرض کردن، حداقل نیازهای کلید خود را بدهید و پاسخ را بررسی کنید.

این نقطه پایانی هیچ شناسه سازمانی را دریافت نمی‌کند. کلید شما در حال حاضر سازمان مربوطه را مشخص می‌کند و پاسخ در همان محدوده ارائه می‌شود.

امتحان کنید

هر چیزی را که داخل براکت‌های زاویه‌دار قرار دارد با مقادیر خودتان جایگزین کنید، و نگهدارنده کلید را با کلیدی از داشبورد خود جایگزین نمایید.

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 در داشبورد شما شناسه سازمان واقعی و کلید خودتان را پر می‌کند و درخواست را روی API زنده اجرا می‌کند تا بتوانید پاسخ واقعی را ببینید. این نقطه پایانی را در کنسول 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.

بدنه درخواست

نامنوعالزامیچیست
trackMarketplaceVerificationTrackبله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…
legal_namestringبله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 and…
countrystringخیرISO-3166-1 alpha-2.
company_numberstringخیر
registered_addressstringخیر
tinstringخیر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. ⛔…
tin_issued_instringخیر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 the…
tin_unavailable_reasonstring<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_addressstringخیر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 would…
accept_self_billingbooleanخیر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 is…
self_billing_vat_statusstring<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_numberstringخیر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…

پاسخ

نامنوعالزامیچیست
verificationMarketplaceVerificationبله
requirementsMarketplaceVerificationRequirementsبله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