Food Delivery apps and their data APIs
Food delivery apps — the restaurant, menu, pricing, and courier-tracking APIs that power every order.
All three apps in this hub are courier-side clients — the data APIs behind the gig rider's earnings, not the consumer menu. DoorDash Dasher exposes per-order earnings (GET /v2/orders/{order_id}/earnings), shift summaries and instant payouts; iFood para Entregadores serves Brazil's couriers an earnings summary, payout history and an advance-pay plan.
Soy Rappi adds the dispatch plane: daily goals, a demand heatmap config and active-order dropoff details for Latin American repartidores. Across all three, the courier session token gates everything, and the wallet and payout endpoints are the most structured data the apps hold.
Frequently asked questions
Why are only courier apps in this hub?
The catalog analyzes the courier-side clients — DoorDash Dasher, iFood para Entregadores and Soy Rappi — because that is where the structured earnings, payout and dispatch data lives. Consumer-facing menu apps are not covered yet.
What earnings data do courier apps expose?
Per-order earnings breakdowns (DoorDash's /v2/orders/{order_id}/earnings), daily and weekly aggregates (iFood's /v1/earnings/summary, Rappi's daily goal), payout history and instant-cashout endpoints. All require the courier's signed-in session.
Do these apps expose dispatch or demand data?
Soy Rappi does most directly: a demand heatmap config and active-order dropoff details. DoorDash exposes shift summaries, and iFood an advance-pay plan — the scheduling and payout rails the gig work runs on.
