KAkairos
Orders

Broadcast your externally-signed on-chain transactions (step 2 of 2)

Hand back the payload_id and one signature per transaction, in the order POST /v2/onchain/intent returned them. The server claims the stored intent atomically (single-use Redis GETDEL — a replay gets 400), re-verifies each signature recovers to the declared owner AND to a wallet registered to you, reassembles the signed transactions, and broadcasts them in nonce order, waiting up to 90 s for each to confirm before sending the next. Partial failure is possible and is reported. If leg i fails to broadcast or revert-checks, the response is a 502 whose message lists the transaction hashes already mined (already broadcast: [...]). Earlier legs stay on chain; re-intent only the remainder. Auth & scope. Identical gate to POST /v2/onchain/intent.

post/v2/onchain/submit

Request

  • Base URL
    https://execution.kairos.trade
  • Auth
    API key in header X-Client-Id and API key in header X-Api-Key and API key in header X-Api-Secret

Request body

payload_idstring uuid required
signaturesstring[] required

One 0x-hex 65-byte signature per transaction, in the same order as transactions[] from the intent. The count must match exactly.

Response

All transactions broadcast and confirmed.

transaction_hashesstring[] required
status'confirmed' required

Always confirmed on a 200 — each transaction is broadcast and waited on (90 s) in nonce order before the next.

Changes

No recorded changes to this operation across all 1 revision of this API.