Skip to main content
The Resolver API is the direction Utexo calls on the resolver. Each resolver defines and configures its own callback URLs; the source documentation does not prescribe paths.
The source does not specify an authentication mechanism for resolver callbacks other than webhook signatures. Do not assume X-API-Key protects this direction. Agree the transport authentication with Utexo before exposing endpoints.

Quote callback

Utexo calls the resolver to request a quote for a user swap.

Request fields

Response

The source describes expected destination minimum and maximum, expiry in milliseconds, and affiliate and intermediate routing data, but does not publish a canonical quote response schema. Confirm the exact shape with Utexo.

Error responses

Use 400 for invalid or unsupported requests and 500 for unexpected resolver failures. Envelope:

Bitcoin deposit PSBT callback

Utexo requests a PSBT for the user’s Bitcoin deposit.

Request

Response

x_only_public_key, refund_control_block, and fast_refund_control_block are only meaningful for deposit_type=escrowed.

Solana co-signed transaction callback

Utexo asks the resolver to co-sign a Solana transaction.

Request

request_type is one of:
  • DepositSwap
  • Fulfill
  • WithdrawToUser
Source fields:
  • intent_id
  • quote_id
  • user_address
  • nonce
  • resolver_deposit
  • token_in
  • token_out
  • secret_hash
  • amount_in
  • deadline
  • resolver_id
  • intermediate_token_out and its bounds (optional)
  • min_amount_out
  • max_amount_out
  • swap_type
  • recent_blockhash (optional)
  • deposit_type = escrowed

Response

The source does not document the Solana co-signed callback response schema. Confirm the response shape with Utexo before implementing.

Fast-refund signing callback

Utexo requests a resolver signature for a fast refund.

Request

Response

The source spells the Bitcoin script field tapscipt. This appears to be a typo of tapscript and must be validated against the current implementation before you wire it up.