Endpoint
Request Body Parameters
The complete response object from the
/hyperevm/route endpoint.
This contains all the necessary information about the optimal route.The address of the input token.Example:
"0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee" for HYPEThe address of the output token.Example:
"0xb8ce59fc3717ada4c02eadf9682a9e934f625ebb" for USDCIf true, the amount parameter represents the desired output amount instead of input amount.
Default:
falseIf true, only direct swaps between the input and output tokens will be considered.
Default:
falseArray of protocol names to exclude from routing.
Default:
[]Maximum acceptable slippage in percentage (0.1 to 49).
Example:
0.5 for 0.5% slippage toleranceThe receiver address for the output token.
Response
The complete response object from the
/hyperevm/route endpoint.
This contains all the necessary information about the optimal route.The hex-encoded calldata to execute the swap through the router contract.
Response Types
Error Responses
Invalid Route
Invalid Slippage
Invalid Signer
Tips
- Always verify the
min_receivedamount matches your expectations - Check that the
destinationaddress is correct - Consider gas costs when splitting across multiple protocols
- Store the route response before requesting calldata
Rate Limits
Please refer to our rate limiting documentation for details about request limits and quotas.Related Endpoints
- Route Endpoint - Get optimal swap routes