# 16 Reporting Audit

Source checked: Uber Eats "Reporting Guide" section shared by you.

## Implemented Now

- Dedicated Reporting route:
  - `POST /api/v1/uber/reporting/fetch`
- 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

## Existing Before

- Store listing and details APIs for installed-store checks
- Order API and operational metrics

## Pending

- Final typed endpoint wrappers for specific reporting reference endpoints once exact paths are shared
- Overnight polling scheduler/job orchestration
- Reconciliation materialization tables for settled vs provisional values