¶ Primary Communication Methods for Rider/Coordinators

Rider/Coordinators have four main methods of communication to interact with drivers during or after a trip:

/get_trip Endpoint:

• Drivers Phone number:

  • Use Driver.phone_number field available in Get Guest Trip endpoint response to let the rider call the rider while the trip is in following status: “ACCEPTED”, “ARRIVING” and “IN_PROGRESS”.

• Pin-Based phone number:

  • Use driver.pin_based_phone_number.phone_number and driver.pin_based_phone_number.pin fields available in Get Guest Trip endpoint response to let the rider call the rider while the trip is in following status: “ACCEPTED”, “ARRIVING” and “IN_PROGRESS”.

/call Endpoint:

• Allows direct calling to the driver of an active or completed trip.
• The provided phone number receives a call from Uber. After picking up, you will be prompted to press “1” to be connected to the driver.
• The phone number you receive the call from is temporary and only valid for the duration of the call.

/communication Endpoint:

• Provides a proxy phone number for voice and SMS communication between the driver and the coordinator.
• This is active only during an ongoing trip, and the session closes once the trip ends.
• The response will contain an output phone number that you can call using your input number to contact the driver.
• Only one session can be active at a time, and calls or SMS messages are not forwarded after the trip ends.

/message Endpoint:

• Sends a text message directly to the driver’s app during an active trip.
• Useful for sending pickup information or other trip-related details.

¶ Guidelines for Using Each Endpoint

/call: Use for direct, immediate contact with the driver via the trip’s UUID and a phone number. Typically useful for post-trip issues, such as lost items.

/communication: Use when you need to contact the driver during an active trip.

/message: Use to send non-urgent information or updates to the driver’s app, which might be seen sooner than answering a call.