Transfers
Confirm Broadcast
Report Solana transaction signatures after broadcasting prepared transactions
POST
After signing and broadcasting the prepared transactions to Solana, call this endpoint to record the signatures. Once the full bundle is recorded the transfer advances toDocumentation Index
Fetch the complete documentation index at: https://dev-docs.multihopper.com/llms.txt
Use this file to discover all available pages before exploring further.
processing and the keeper network takes over.
This endpoint is resumable and called twice in the normal flow:
- Immediately after
keeperFundingTx— call with justkeeperFundingSignatureand an emptyrouteInitSignatures: []. This prevents the keeper from being double-funded if deployment is later resumed. - After all remaining transactions — call with
routeInitSignatures,orchestratorInitSignature, andsessionInitSignatures.
Path parameters
The internal transfer ID.
Request body
Base58 signatures for each
routeInitTxs entry. Pass an empty array [] on the intermediate call (after keeper funding only).Base58 signature for
keeperFundingTx. Required whenever /prepare emitted a keeperFundingTx — omitting it returns MH_039.Base58 signature for
orchestratorInitTx. Omit when that field was null.Base58 signatures for each
sessionInitTxs entry. Omit when empty.Response
Updated transfer object.
status becomes processing once the full bundle is recorded.
