Skip to main content

Uber Direct plugin

The fixed Dashboard renders Plugin settings from returned key_plugin configuration categories. Uber Direct category presence, authentication, schema, and delivery behavior are external/deployed boundaries.

Plugin settings navigation showing Uber Direct without credential values

Historical schema evidence​

Preserved project evidence recorded a production credential group:

  • Organization ID
  • Client ID
  • Client Secret

It also recorded sandbox equivalents and these external-schema labels:

  • Sandbox Mode
  • Add Delivery Fee
  • Accept Cash Orders
  • Cancel Reason (sandbox)
  • Enable Dropoff Verification (pincode)
  • Business Name
  • Sync ETA Time

These names do not establish current installation, values, required state, validation, environment selection, provider account, or delivery behavior. Credentials and identifiers remain excluded.

Fixed category and mutation boundary​

AllSettings passes returned plugin categories to SettingsMenuOptions; a numeric category opens generic SettingsList. Config edits stage locally and Save persists changed items sequentially; type-5 image configs use an immediate save path. The separate Connect source recognizes key uber_direct_integration, but that comparison does not prove category presence, provider availability, fee/cash/ETA/cancellation/pincode semantics, dispatch, tracking, or location effects.

API-core declares config category/item and plugin contracts. The separate Developers → Plugins manager owns install/root/iframe actions. No runtime read, provider setup, delivery, dispatch, assignment, verification, tracking, config/image write, or plugin-manager mutation ran.

Credentials and delivery data

Credentials, roots/endpoints, stores, orders/deliveries, addresses, customers, drivers/locations, quotes, statuses, callbacks, and provider responses remain excluded.

Source-only boundary​

  • /all-settings is level-0 routed; Plugin settings depends on returned plugin categories.
  • The retained screenshot is sanitized historical navigation evidence, not current installation/configuration proof.
  • No runtime/GET/HEAD, write, plugin/provider action, order/delivery, PII, location, payment, job, or outbound call ran.
  • Re-entry requires immutable Dashboard/API and Uber Direct serving receipts plus a credential-free synthetic category fixture with config reads/writes, provider egress, orders, deliveries, locations, and callbacks intercepted.

Related guides: Delivery services · Developers