marketplace

POST `/v1/marketplace/vendor/payout-methods`

Propose a destination to be paid at.

Autenticazione

Invia una chiave API come bearer token. Questo endpoint non specifica un permesso specifico nella specifica, quindi assegna alla tua chiave i permessi minimi necessari e verifica la risposta invece di fare supposizioni.

Questo endpoint non richiede alcun ID organizzazione. La tua chiave identifica già l'organizzazione a cui appartiene e la risposta è limitata ad essa.

Provalo

Sostituisci qualsiasi elemento tra parentesi angolari con i tuoi valori e il segnaposto key con una chiave dalla tua dashboard.

curl -X POST https://api.zinndigital.com/v1/marketplace/vendor/payout-methods \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "rail": <string> }'

Hai effettuato l'accesso? La console API nella tua dashboard inserisce il tuo ID organizzazione reale e la tua chiave personale, ed esegue la richiesta sull'API live in modo da poter vedere la risposta effettiva. Apri questo endpoint nella console API

Dettagli

docs/82 §7c. The row is created **unverified** and can receive nothing: only staff verification makes it payable, and then only after the 48-hour cooling-off. ⛔⛔ **A change of destination is a new row, never an edit** — there is deliberately no endpoint that changes `destination` on an existing one. §7c: *"Change of payout details is the account-takeover cash-out route, and must be treated as one."* Editing a verified row would keep its verified state and its long-expired hold while pointing the money somewhere nobody looked at. ⭐ Re-adding a destination the seller already has returns the existing row rather than minting a second one — otherwise "change it and change it back" resets the cooling-off clock in two requests. ⛔ The **network** is its own field, not part of the address. Sending USDT TRC20 to a BEP20 address loses the money irrecoverably, so the same address on two networks is two destinations, each earning its own proof and its own hold.

Corpo della richiesta

Nome	Tipo	Obbligatorio	Che cos'è
`rail`	`string`	Sì	—
`destination`	`string`	No	Empty for account credit, which has nowhere to send.
`network`	`string`	No	—
`label`	`string`	No	—

Risposta

Nome	Tipo	Obbligatorio	Che cos'è
`id`	`string`	Sì	—
`rail`	`string`	Sì	—
`rail_name`	`string`	Sì	—
`destination`	`string`	Sì	⛔ Masked, always. Enough to recognise which account this is, never enough to reproduce it. The whole value never leaves the engine on a read path.
`network`	`string`	Sì	⛔ Its own field, never folded into the address. Sending USDT TRC20 to a BEP20 address loses the money irrecoverably (docs/82 §7b), so the network is part of the destination's id…
`label`	`string`	Sì	—
`state`	`MarketplacePayoutMethodState`	Sì	Where one destination is in its own verification (docs/82 §7c). `retired` rows are kept rather than deleted — a payout that went there is explained by them.
`proof_kind`	`MarketplacePayoutProofKind`	Sì	How ownership of the destination was shown. ⛔ Crypto is the honest exception and is recorded as one: docs/82 §7c states that no document can prove wallet ownership, so a signe…
`rejection_reason`	`string`	No	—
`is_default`	`boolean`	Sì	—
`verified_at`	`string`	No	—
`hold_until`	`string`	No	docs/82 §7c's 48-hour cooling-off on the first payout to this destination — long enough for the change notice to land, short enough that a seller who genuinely changed bank…
`permitted_proof_kinds`	`MarketplacePayoutProofKind[]`	Sì	—

Errori che questo endpoint può restituire

401 · 404 · 422

POST /v1/marketplace/vendor/payout-methods