Allowance & permit

GET /v1/allowance and POST /v1/permit.

Allowance

GET/v1/allowance?chainId=1&token=0x…&taker=0x…&amount=…

amount is required, in raw units: the quote's input.amount. Missing, negative, fractional or non-numeric values return bad_request rather than a 200 with nulls in it. "0" is accepted and asks whether any allowance exists at all.

Response

Field	Type	Description
required	boolean	True if an approve is needed first. Always a boolean, never `null`: false for the native asset and where the router is not deployed, with `reason` saying which.
allowance	string	Current allowance, raw.
spender	string	Exactly what to approve.

requiredboolean

True if an approve is needed first. Always a boolean, never null: false for the native asset and where the router is not deployed, with reason saying which.

allowancestring

Current allowance, raw.

spenderstring

Exactly what to approve.

Permit

POST/v1/permit

json

{ "chainId": 1, "token": "0x…", "owner": "0x…" }

Returns EIP-2612 typed data for signing, or PERMIT_UNSUPPORTED with the Permit2 address for tokens that do not implement it. See Approvals for the flow.

Submit

Tokens & prices