marketplace

POST /v1/marketplace/vendor/verification/subjects/{subject_id}/identity-check

Start (or resume) this person's Stripe Identity check.

All marketplace endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

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 POST https://api.zinndigital.com/v1/marketplace/vendor/verification/subjects/{subject_id}/identity-check \
  -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 identity check is the payout gate (owner, 2026-11-13): a seller approved to sell verifies the identity of each person on the file once their first payout is due. Returns the provider's hosted page to send the seller to; url is null when the check is already with the provider and nothing is left for the seller to do. The return URL is built by the server, never taken from the request. Refusals (422, details[].code): NOT_SUBMITTED (no submitted or automatically approved file), PAYOUT_NOT_DUE, NOT_IN_GOOD_STANDING, ALREADY_VERIFIED; none of them opens a paid session. An open session is resumed, never paid for twice.

Parameters

NameTypeRequiredWhat it is
subject_id (path)stringYes—

Response

NameTypeRequiredWhat it is
urlstringYes—
statestring<created, requires_input, processing, verified, canceled>Yes—

Errors this endpoint can return

401 · 404 · 422 · 503