Platform report catalogue
Phase 2. Reporting is fetchReportCoverage (what you can request), createReport (request one), fetchReports (list and poll) and fetchReport (get one, with its signed download URLs). This page is the catalogue those operations serve.
Phase 2 reporting delivers each platform's native report files, exactly as the platform produces them. You request by platform and by the platform's own report-type value, and you receive the platform's own CSV.
The formats belong to the platforms. Report contents, columns and formats are defined by the delivery platforms and change on their schedule, not ours. Parse CSVs by header name and tolerate new columns. For authoritative field-level detail, follow the platform's own documentation. A normalized, platform-independent query surface over this data is on our roadmap with no phase committed; until then this API's value is programmatic retrieval, not reformatting.
Uber Eats
Nine report types. Request windows differ per type — some are range-capped, others are a rolling lookback.
| Report type | Contents | Window constraint |
|---|---|---|
PAYMENT_DETAILS_REPORT | Payout / reconciliation detail | Range ≤ 30 days |
FINANCE_SUMMARY_REPORT | Financial summary | Range ≤ 30 days |
ORDERS_AND_ITEMS_REPORT | Order and line-item detail | Range ≤ 15 days |
ORDER_HISTORY_REPORT | Order history | Lookback window ~T-188 to T-2 |
ORDER_ERRORS_MENU_ITEM_REPORT | Item-level order errors | Lookback ~T-188 to T-2 |
ORDER_ERRORS_TRANSACTION_REPORT | Transaction-level order errors | Lookback ~T-190 to T-4 |
DOWNTIME_REPORT | Storefront downtime | Lookback ~T-188 to T-2 |
CUSTOMER_AND_DELIVERY_FEEDBACK_REPORT | Raw customer and delivery feedback | Lookback ~T-188 to T-2 |
MENU_ITEM_FEEDBACK_REPORT | Raw menu-item feedback | Lookback ~T-188 to T-2 |
Platform mechanics worth knowing, because they shape what we can promise: output is CSV; financial data may take up to roughly 72 hours to settle, and disputes can surface after 30 days; refunds and chargebacks appear only in reporting and never in the order feed. That last one is why reconciliation belongs on reports rather than on real-time order data.
Official reference: Uber Eats' own reporting API documentation.
Grubhub
Nine report types, one type per request, up to one year of data per request.
| Report type | Contents | Data available from |
|---|---|---|
order-details | Order-level detail | 2023-01-01 |
transactions | Transaction ledger (near-real-time, ~5-min freshness) | 2020-01-01 |
deposits | Deposit summaries | 2020-01-01 |
deposit-details | Deposit line detail | 2020-01-01 |
financials-summary | Financial summaries | 2020-01-01 |
cancellations | Cancellations | 2023-01-01 |
product-mix | Item / product mix | 2023-01-01 |
operations-summary | Operational summary | 2023-01-01 |
order-adjustments | Adjustments and disputes (30-day dispute window) | 2023-01-01 |
Every type except transactions refreshes once daily.
Official reference: Grubhub's own available-reports documentation.
DoorDash
Programmatic report access on DoorDash is a platform-side constraint for our integration category: DoorDash does not currently provide it. fetchReportCoverage reflects that state directly — DoorDash rows return unavailable, with the reason — and the interim path is the DoorDash merchant-portal CSV export. We are pursuing platform-side enablement, and a change will appear in the Changelog. Uber Eats and Grubhub reporting are unaffected.
See Coverage and limitations for the full per-platform matrix.
Feedback files are not a reviews API
The two Uber Eats feedback report types above deliver raw CSV files of feedback data. That is not a normalized reviews-and-ratings API — structured review objects joined across platforms — which remains on the roadmap with no phase committed. Naming the difference here so no integration is built on the assumption that the first is the second.