21 lines
624 B
Markdown
21 lines
624 B
Markdown
# Uber Wrapper Developer Portal
|
|
|
|
## Goal
|
|
|
|
Create one generic POS-facing wrapper that can integrate with Uber for many restaurants, each with its own Uber OAuth connection.
|
|
|
|
## Architecture Summary
|
|
|
|
1. Merchant is created in wrapper.
|
|
2. Merchant connects Uber account via OAuth.
|
|
3. Wrapper stores tokens and proxies requests to Uber APIs.
|
|
4. POS uses wrapper APIs only.
|
|
5. Uber webhooks are ingested by wrapper and routed to internal logic.
|
|
|
|
## Key Benefits
|
|
|
|
- Your POS is isolated from Uber API complexity.
|
|
- You can add custom business logic centrally.
|
|
- You can support many merchants with one standard integration path.
|
|
|