UBER-EATS-Wrapper/docs/developer-portal/03-integration-configuration-flows-audit.md

03 Integration Configuration Flows Audit

Source checked: Uber Eats "Integration Configuration Flows" section shared by you.

Implemented Now

• Merchant OAuth based store retrieval:
  • GET /api/v1/uber/stores/provisionable
  • Uses merchant token (authorization_code / eats.pos_provisioning)
• Store activation via POS data:
  • POST /api/v1/uber/stores/{storeId}/pos-data
• Retrieve integration configuration:
  • GET /api/v1/uber/stores/{storeId}/pos-data
• Store integration update/deactivation:
  • PATCH /api/v1/uber/stores/{storeId}/pos-data
• Store de-provision:
  • DELETE /api/v1/uber/stores/{storeId}/pos-data
• Webhook provisioning-state reaction:
  • store.provisioned marks mapped connection active
  • store.deprovisioned marks mapped connection deprovisioned

Existing From Earlier

• OAuth authorization URL + callback
• Merchant connection persistence
• Webhook ingestion and persistence

Pending

• Strong store mapping workflow (location-data assisted matching UI flow)
• Strict nested schema validation for deeper webhook config object variants
• Automated post-provisioning follow-up actions (e.g., mandatory menu upload jobs)