Skip to main content
POST
Accept 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:accept
sponsorship:use

Headers

Idempotency-Key
string<uuid>
required

Lowercase UUIDv7 that names this acceptance: it becomes the acceptance_id. Choose it before the first send and reuse it on every retry. The same key, quote and body returns the stored acceptance without restarting its deadline; the same key with another quote or body returns 409 IDEMPOTENCY_KEY_REUSED. Keys are unique per taker account, across all quotes. A quote can be accepted once: a new key on an RFQ that already has a live acceptance returns 409 STATE_CONFLICT, or 409 ACCEPTANCE_IN_FLIGHT while an entry acceptance awaits its maker or its trade; the same answer refuses any other entry quote the account accepts meanwhile. Lost the response? Read GET /v1/quotes/{quote_id}/acceptance instead of accepting again.

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

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

The taker's accept of the quote in the path. The Idempotency-Key header becomes the acceptance_id.

taker_signature
string
required

Your EIP-712 signature over the quote. For an entry quote, sign its entry terms as TakerAccept. For a cash-out quote, the owner signs quote_id as SellBack, the same digest the maker signs.

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

Entry quotes only; not allowed on a cash-out. Pays the part of the stake your vault balance is short from your account wallet: WALLET with a USDC authorization for the exact shortfall, or WALLET_APPROVAL from the wallet's approval to WalletAccept. Omit it when your vault balance covers the stake. The acceptance keeps the route it was admitted with; a replay never switches it.

Response

The acceptance after the maker answered or the two-second confirm window closed, returned within three seconds. Its status is ACCEPTED, DECLINED, TIMED_OUT or CANCELLED, never PENDING_CONFIRM. ACCEPTED means the trade is queued, not yet on chain: follow OPERATION_UPDATED on the account stream until it ends. Only COMMITTED opened the position; an operation that ends EXPIRED_UNEXECUTED or REVERTED traded nothing, and its failure_reason says why when known.

The accept response: the acceptance after the maker answered or the deadline passed.

acceptance_id
string<uuid>
required

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

Status after the maker answered or the deadline passed. Never PENDING_CONFIRM.

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$
server_time
string<date-time>
required

The database clock that sets fund_by and deadline, read with this acceptance, as an RFC3339 UTC timestamp. Judge them against it, not the local clock: the venue's time now is at most server_time plus the time elapsed since you sent the request (take the larger of a monotonic and a wall clock's elapsed time). Setting your clock to server_time when the response arrives reads early by the response's delay and can send too late. The accept response is held for the maker's answer, so a GET /v1/rfqs/{rfq_id}/quotes sent alongside it gives a tighter bound from its own server_time; keep the tightest. Send nothing timed by fund_by without a response to judge it by.

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$
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$
funding_failure_reason
enum<string>

Only on an acceptance funded WALLET_APPROVAL whose operation ended EXPIRED_UNEXECUTED with failure_reason INSUFFICIENT_CASH because the wallet fell short. INSUFFICIENT_APPROVAL: the wallet's approval to WalletAccept was below the shortfall; approve more (GET /v1/me/wallet-approval). INSUFFICIENT_WALLET_USDC: the wallet held less USDC than the shortfall, including a HyperCore move that did not land by fund_by. Absent when vault cash fell short or the venue could not tell.

Available options:
INSUFFICIENT_APPROVAL,
INSUFFICIENT_WALLET_USDC