marketplace
GET /v1/marketplace/vendor/verification
The seller's identity file and what it still needs.
Authentication
Send an API key as a bearer token. This endpoint checks no specific permission, so any key for your organisation can call it.
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/verification \
-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
⛔ The sanctions/PEP screening result is not in this payload. Telling someone they are a possible match is tipping-off; only the decision reaches the seller, through state.
Response
| Name | Type | Required | What it is |
|---|---|---|---|
verification | MarketplaceVerification | Yes | — |
requirements | MarketplaceVerificationRequirements | Yes | 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. |
Errors this endpoint can return
401 · 404