Uber opens its RUSH API to all, letting developers add on-demand delivery to their products
We started the Uber Developer Platform to make it easy for any developer to get their users from A to B. With the launch of a private UberRUSH API beta in January, we expanded that mission to include …
Context & Ripple Effects
UberRUSH began as a courier service when Uber launched it in Chicago and San Francisco in October 2015 (UberRUSH goes live), extending a developer strategy that started earlier that year when Uber let any app embed its ridesharing service (the ridesharing embed program). Opening the RUSH API beyond January's private beta turns that same playbook toward physical goods: any developer can now wire on-demand delivery into their product rather than build a courier network.
The move matters because it converts Uber's courier fleet into infrastructure other companies build on — but the corpus also shows how the bet resolved: Uber shut UberRUSH down entirely by mid-2018 (the UberRUSH shutdown) and redirected its B2B energy toward verticals like healthcare rides (Uber Health).
First-order effects
- Developers and small merchants can now add sub-30-pound on-demand delivery to their apps without operating couriers, using new per-user API keys with granular permissions, request-signing secrets, and IP whitelisting.
- Uber gains a distribution channel where third-party products generate delivery volume its courier fleet would not otherwise see.
Second-order effects
- Incumbent local couriers and point solutions compete against an API whose cost is bundled into products they don't control, pressuring standalone delivery pricing.
- Merchants that integrated RUSH inherit platform risk: their checkout flows depend on Uber's willingness to keep subsidizing a low-margin courier business.
Third-order effects
- The arc from open API to full shutdown suggests that embedding logistics as a feature does not make the underlying fleet economics work — platformization amplifies demand but also exposes unit costs, pushing Uber toward curated B2B verticals like healthcare instead of horizontal delivery.
- If the pattern holds, on-demand logistics consolidates around players who can cross-subsidize fleets from adjacent high-margin businesses, while pure API-delivery plays need either scale or vertical focus to survive.
The trend: Mobility companies are turning vehicle fleets into programmable API platforms, though UberRUSH's trajectory shows the delivery variant of that model struggling without a profitable core to lean on.