marketplace
GET /v1/marketplace/vendor/payout-readiness
Whether money may leave the platform to this seller, and why not.
Authentication
Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.
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/vendor/payout-readiness \
-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/82 §7a: *"the vendor is told exactly why and what to do."* ⭐ The same computation the payout runner performs, rendered for the seller. One producer, two audiences — a screen that re-derived the reasons would drift from the gate, and the drift would show as a seller told they are ready while the runner refuses. ⛔ Verification is optional until the first payout and then mandatory. An unverified seller may list, sell and be accepted; it is the **payout** that is held, never the sale.
Response
| Name | Type | Required | What it is |
|---|---|---|---|
permitted | boolean | Yes | — |
reasons | string<no_verification, verification_not_approved, document_expired, document_missing, subject_not_approved, sanctions_not_screened, sanctions_not_clear, document_request_holds_payouts, vendor_not_approved, no_destination, destination_cooling_off, dac7_data_incomplete>[] | Yes | Every reason at once, not the first — a seller told one problem at a time makes one round trip per problem. |
Errors this endpoint can return
401 · 404