Skip to main content

Speed sells fall back to the relayed route, and unlisted tickers leave the stocks reads

A priority: "speed" sell on Robinhood Chain or Base that the speed route cannot price is now quoted on its relayed route, with a new speed_route_fallback warning, where the position used to be left out or the quote refused. One Action item, for callers that send priority: "speed" on POST /quote/sell. Separately, a ticker that no venue lists a token for is no longer served by the stocks reads.

What changed​

Action: a speed sell can return a relayed leg. When the speed route answers no_routes for a robinhood or base position on /quote/sell, that leg is in quotes[] on its relayed route.

  • The leg has gasless: true and one typed-data payload, also when you sent execution: "user_operation". Its fill can take minutes, not one block.
  • warnings[] carries speed_route_fallback for it, with chain, protocol, reason (no_routes), approval_needed and approval_spender.
  • approval_needed: true means the order cannot fill until the wallet approves the stock token to approval_spender. A relayed order never bundles an approval and this API does not send it for you: POST /trade/submit may refuse the order as not_enough_balance_or_allowance, or it stays pending and expires unfilled. false means the allowance covers the sale, and null that it could not be read.
  • The warning is sent only for a leg the response carries. A position the relayed route priced but another leg outranked reads speed_route_unavailable with reason: "no_routes".
  • Buys are unchanged: a leg the speed route cannot serve is still absent, with speed_route_unavailable.

speed_route_unavailable repeats less. It is sent once per chain and reason (once per chain/protocol pair for no_speed_venue, and once in all for disabled).

A ticker with no listing is not served. A ticker that no venue lists a token for is left out of GET /stocks, GET /stocks/tickers and every other stocks read.

extension in the reference. The typed-data payload schema documents an extension field. This API never sends it, so there is nothing to handle.

Skill version. The treasures-b2b-api skill is 1.23.0.

What to do​

  • Action: if you send priority: "speed" on a sell and assume every leg is a transaction to sign whole, branch on gasless (or the payload type) per leg, and handle approval_needed before you submit a relayed leg.
  • The guides are Routing and Priority Mode and Buying and Selling.