Report the vault deposit for an arrived transfer
POST/api/v1/bridge/intents/:intent_id/deposit-tx
Only from the delivered state, and only on a deposit journey. The hash is recorded here and proven against the vault listener's processed deposits before anything is credited. A hash the vault listener has already mirrored for another account is refused with deposit_tx_not_owned; a hash it has not seen yet is accepted, because the user posts it seconds after they sign.
Request
Responses
- 200
- 400
- 401
- 404
- 409
- default
The transfer with the deposit recorded
The transaction hash is not a non-zero 32-byte hash, or it is a deposit that belongs to another account (deposit_tx_not_owned).
Missing, invalid, or expired read tokens.
No such transfer for this account.
The transfer is not in the delivered state, or is not a deposit journey.
Error response. Prefer the nested ApiErrorResponse via X-SC-Error-Format: envelope-v1; existing unnegotiated handler responses can retain a documented legacy flat shape through the compatibility period.
Response Headers
Stable request correlation id generated or echoed by the server.