35 lines
1.2 KiB
Markdown
35 lines
1.2 KiB
Markdown
# 16 Reporting Audit
|
|
|
|
Source checked: Uber Eats "Reporting Guide" section shared by you.
|
|
|
|
## Implemented Now
|
|
|
|
- Dedicated Reporting route:
|
|
- `POST /api/v1/uber/reporting/fetch`
|
|
- `POST /api/v1/uber/reporting/create`
|
|
- Uses `eats.report` client-credentials scope.
|
|
- Retry policy implemented for safe transient failures only:
|
|
- `429`, `408`, `500`, `502`, `503`, `504`, and network errors
|
|
- total attempts: 4 (initial + 3 retries)
|
|
- exponential backoff + jitter
|
|
- CSV ingestion strategy aligned:
|
|
- parse by header names
|
|
- ignore unknown extra columns
|
|
- tolerate missing columns with null/default behavior
|
|
- report missing required headers in response metadata
|
|
- Marketplace Reporting API async flow aligned:
|
|
- `POST /v1/eats/report` wrapper support with report-type/date constraints
|
|
- workflow tracking via `workflow_id`
|
|
- webhook completion handling for `eats.report.success`
|
|
- report sections metadata persisted on completion
|
|
|
|
## Existing Before
|
|
|
|
- Store listing and details APIs for installed-store checks
|
|
- Order API and operational metrics
|
|
|
|
## Pending
|
|
|
|
- Overnight polling scheduler/job orchestration for report section downloads
|
|
- Reconciliation materialization tables for settled vs provisional values
|