Skip to main content
POST
Confirm quote

Authorizations

Authorization
string
header
required

Scoped API key (ttk_...), created in the Totalis app or by a wallet-session user through the API keys routes with a fresh wallet signature; those routes never accept a key. Each key acts for one account, yours or a maker's, and holds only scopes that account can use. Each operation lists the scopes it requires. Send no Origin.

Scopes

quote:write

Path Parameters

quote_id
string
required

The quote's quote_id, from QUOTE_CREATED, QUOTE_ACCEPTED or Create quote.

Pattern: ^0x[0-9a-f]{64}$

Body

application/json

Your answer to the acceptance, before its deadline, two seconds after the accept: CONFIRM with your signature, or DECLINE. Send no Idempotency-Key: the quote identifies its one acceptance.

decision
any
required

Confirm and sign the accepted terms; the trade executes.

maker_signature
string
required

Your quote signer's EIP-712 signature over the accepted terms: entry as Quote, sell_back as SellBack. Your capital stays reserved for as long as this signature can execute.

Pattern: ^0x(?:[0-9a-f]{2}){1,4096}$

Response

The acceptance after your answer. ACCEPTED means the trade is queued, not yet on chain, and carries its operation_id.

The acceptance after your answer. It never includes the taker's acceptance_id.

quote_id
string
required

The accepted quote. A quote has at most one acceptance.

Pattern: ^0x[0-9a-f]{64}$
rfq_id
string<uuid>
required

RFQ the quote answers.

Pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-7[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$
status
enum<string>
required

PENDING_CONFIRM: waiting for the maker. ACCEPTED: the maker confirmed and the trade is queued as operation_id. FILLED: the trade committed on chain. FAILED: it reverted or expired unexecuted; read GET /v1/me/operations/{operation_id}, whose failure_reason is INSUFFICIENT_CASH when the taker's Cash fell short. DECLINED: the maker declined. TIMED_OUT: the maker did not answer by deadline. CANCELLED: the quote or RFQ went away first.

Available options:
PENDING_CONFIRM,
ACCEPTED,
FILLED,
FAILED,
DECLINED,
TIMED_OUT,
CANCELLED
deadline
string<date-time>
required

When the maker's time to confirm ends, two seconds after the accept, as an RFC3339 UTC timestamp.

Maximum string length: 30
Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}([.][0-9]{1,9})?Z$
acceptance_id
string<uuid>

The Idempotency-Key the taker sent with the accept, which names this acceptance. Never sent to the maker.

Pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-7[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$
operation_id
string

The on-chain operation that executes the trade; present once status is ACCEPTED, FILLED or FAILED.

Pattern: ^0x[0-9a-f]{64}$
fund_by
string<date-time>

For an acceptance with funding, once the maker confirmed: send any HyperCore to wallet transfer that funds it before this time, two seconds after the confirm, as an RFC3339 UTC timestamp. Send the transfer only after the accept answers ACCEPTED, never before it: an accept answered any other way trades nothing. Save the signed transfer before its first send and resend the same bytes while Hyperliquid has not answered, until fund_by. After it, discard an unsent transfer. A transfer sent in time has two more seconds to land; if the wallet still lacks the funding then, the operation ends EXPIRED_UNEXECUTED with failure_reason INSUFFICIENT_CASH, or SIMULATION_REVERTED at once if the funding authorization was already used or canceled. Judge fund_by by the bound server_time describes, never the local clock. Never sent to the maker.

Maximum string length: 30
Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}([.][0-9]{1,9})?Z$