Three lines

Uber

Developers

Journey For Integration

Privileged and Confidential This endpoint design has been confidentially shared with you. It is still under development and is subject to change without notice. Please do not share this document or API endpoint details with anyone who is not authorized to have access. For more information read about scopes.

Sample Journey for a Supplier: From Planning to Successful Integration of the First API

Day 1: Initial Planning and Setup

Task 1: Integration Kickoff Meeting

  • Details: Conduct an initial meeting to discuss the integration process, expectations, and timelines.
  • Owner: Supplier’s POC and Uber’s Operations Team

Task 2: Sign Integration Contract

  • Details: Finalize and sign the contract with the supplier to formalize the partnership.
  • Owner: Supplier and Uber’s Business Development/Ops Team

Task 3: Configure Supplier Organizations in Uber’s Internal System

  • Details: Set up supplier organizations within Uber’s internal system, with the assistance of the Uber point of contact (POC).
  • Owner: Uber’s Operations Team
Day 2: Development and Configuration

Task 4: Create Uber Developer Account and Application

  • Details: The supplier needs to create a developer account and register an application on Uber’s platform.
  • Owner: Supplier
  • Note: Suppliers must provide the developer account owner’s email and Client ID to Uber for configuration.

Task 5: API Scopes Allowlisting

  • Details: Identify and allow the necessary API scopes required by the supplier.
  • Owner: Uber’s Operations Team
  • Duration: 10–15 days
  • Note: Suppliers need to submit the use-case and usage pattern to uber’s operations team.

Task 6: Add Supplier Applications Owner as Root Org Admin

  • Details: Include the supplier application owner’s email as an admin in the root/HQ organization on Ops-Garage.
  • Owner: Uber’s Operations Team
Day 3: Integration and Testing

Task 7: Configure Uber Services for the App

  • Details: Securing internal approvals with respect to compliance and legal terms.
  • Owner: Uber’s Operations Team
  • Duration: Approximately 5–10 days
  • Note: Once the configuration is completed on uber’s end, suppliers can begin testing the APIs and report any issues or concerns that arise.

Task 8: Enable Webhook Events

  • Details: If required by the supplier, enable webhook events like driverStatusChange or vehicleStatusChange.
  • Owner: Uber’s Operations Team
  • Duration: 1 - 4 days

Task 9: Create Test Account for Supplier

  • Details: Set up driver test accounts for the supplier to facilitate testing in sandbox/production environments.
  • Owner: Uber’s Operations Team
  • Duration: 30 Minutes
Day 4: Launch

Task 10: Complete the Launch

  • Details: Finalize all configurations and testing, and officially launch the integration.
  • Owner: Uber’s Operations Team

Journey

Uber

Developers
© 2023 Uber Technologies Inc.