兴趣爱好============================
DiDi Delivery Data API: Courier Trips, Wallet and Payout Data Integration
============================
Turn DiDi Food courier jobs, balances and cash-outs into callable open data.
--------------------
INTRODUCTION
--------------------
Food delivery in Latin America runs on independent couriers. They often switch between several platforms for the same shifts. In Mexico and Chile, riders may run DiDi Delivery next to Soy Rappi and Uber Eats. Fleet operators and finance teams have no clean way to see what happens inside these courier apps. That gap is where a food delivery data API helps.
--------------------
FEATURED APP
--------------------
DiDi Delivery: Deliver & Earn is DiDi Global's courier app for DiDi Food. Riders pick up restaurant orders and drop them off on foot, by bicycle or by scooter. They sign up with a mobile number, upload identification, and complete an in-person check at a DiDi Courier Center. After that they can accept jobs, review trip income and cash out through DiDi Pay and the in-app wallet.
The openData Studio page documents 17 endpoints. They cover:
• login and ticket refresh
• rider profile
• live trip detail
• hot-zone order forecast
• wallet balances and statements
• KYC status
• withdraw quotes and tracking
--------------------
WHAT CAN BE INTEGRATED
--------------------
• Trips: pickup takeInfo (shopName, shopAddress, cashAdvances) and drop-off SendInfo (customerName, cashReceivable, isPhoneProtect)
• Rider identity: ID, realname, phone, workType, cityID and countryCode
• Balances: accountBalance.balance, totalBalance, totalEarning and cashback
• Statements: transId, transDate, businessType and amountText
• Cash-out: quotes with channelName, inputAmount and commissionAmount, plus progress by withdrawId
• Compliance: kycStatus, fullKycStatus and bound bindCard bank rows
--------------------
USE CASES
--------------------
[1] Live trip overlay
• A fleet board shows the current DiDi Food pickup and drop-off.
• It reads takeInfo and cashReceivable without scraping the courier screen.
[2] Wallet reconciliation
• Nightly jobs read the balance and statement lines.
• Fleet or tax tools match DiDi Food payouts against their own ledger.
[3] Cash-out operations
• Payout desks use the calculate step to read the commission.
• They then settle on availableBalance, canWithdraw and bindCard details.
[4] KYC gate for withdrawals
• Compliance overlays watch kycStatus, fullKycStatus and authenticationStatus.
• They also check rider ID, realname and workType before cash-out is enabled.
[5] Payout tracking
• Support teams follow a withdrawal through its status and predictionTime.
• They can see the bank name and card for each request.
--------------------
DELIVERY & PRICING
--------------------
✓ Scoped integrations start from USD 500 with source-code handoff
✓ Hosted access billed per call is also available
✓ Delivery in 3–7 days
✓ Payment only after acceptance, with an NDA and SOW on every engagement
The page notes that work is scoped to authorized use. It also says the endpoint examples are reconstructed from the app's interface and are illustrative, not a live capture.
--------------------
CONCLUSION
--------------------
DiDi Delivery holds the trip, wallet and payout data that fleet, finance and compliance teams need. openData Studio packages it as a documented data API. See the full endpoint list, fields and FAQ here:
https://opendata-studio.com/apps/didi-delivery/
Ready to connect DiDi Delivery data to your dashboard or ledger? Use the page above to get a quote.
