marketplace

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

Propose a destination to be paid at.

Аутентификација

Пошаљите API кључ као bearer токен. Ова крајња тачка не наводи конкретну дозволу у спецификацији, па свом кључу доделите најмања неопходна овлашћења и проверите одговор уместо да претпостављате.

Ова крајња тачка не прихвата id организације. Ваш кључ већ идентификује организацију којој припада, а одговор је ограничен на њу.

Испробајте

Замените све што је у угластим заградама сопственим вредностима, а чувар места кључа кључем са своје контролне табле.

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> }'

Пријављени сте? API конзола на вашој контролној табли попуњава ваш прави id организације и ваш сопствени кључ, и покреће захтев према живом API-ју како бисте могли да видите стварни одговор. Отворите ову крајњу тачку у API конзоли

Детаљи

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.

Тело захтева

Назив	Тип	Обавезно	Шта је ово
`rail`	`string`	Да	—
`destination`	`string`	Не	Empty for account credit, which has nowhere to send.
`network`	`string`	Не	—
`label`	`string`	Не	—

Одговор

Назив	Тип	Обавезно	Шта је ово
`id`	`string`	Да	—
`rail`	`string`	Да	—
`rail_name`	`string`	Да	—
`destination`	`string`	Да	⛔ 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`	Да	⛔ 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…
`label`	`string`	Да	—
`state`	`MarketplacePayoutMethodState`	Да	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`	Да	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 signed…
`rejection_reason`	`string`	Не	—
`is_default`	`boolean`	Да	—
`verified_at`	`string`	Не	—
`hold_until`	`string`	Не	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[]`	Да	—

Грешке које ова крајња тачка може вратити

401 · 404 · 422

POST /v1/marketplace/vendor/payout-methods