¶ Sandbox Testing

Using Sandbox Runs:

Sandbox runs allow for temporary testing of drivers and riders, with a session lasting 8 hours.

Common errors:

• Invalid Run ID: Happens if the Get Sandbox Run endpoint is called within 1 minute of sandbox creation or if mismatched lat/long values are used for driver and pickup locations. Errors during sandbox runs invalidate the run.

Changing Driver Status:

When testing in sandbox, ensure the driver status is updated quickly (within seconds) after creating the trip. Failing to do so may cause a timeout error. Solution: Make the driver-accept state change call immediately after creating the trip.

¶ Production Features

Automated Calling for Riders:

Riders receive automated phone calls with trip information when a driver is matched. To disable automated calling, set call_enabled to false in the API request.

Sharing Trip Status:

Riders can share their trip status with others (e.g., emergency contact or a friend) by providing their contact details via contacts_to_notify[]. Provide the phone number in contacts_to_notify[].phone_number and specify the event in contacts_to_notify[].contact_event.

Handling Trips That Require Attention:

Highlighting trips needing intervention can improve the rider experience. Some examples of such trips:

• Driver Canceled: The driver canceled the ride.
• No Driver Found: No driver was available for the request.
• Driver Waiting: The driver has been waiting for over 2 minutes for the rider.
• Long Match Time: It’s taking too long to match a driver.

Coordinator Actions:

Depending on the situation, coordinators can:

• Request a new trip.
• Find an alternative solution.
• Notify the rider of delays.
• Assist the rider in locating the driver.

¶ Tracking and Flagging Important Trips

• Canceled Trips: Use Get Guest Trip endpoint or webhooks to track when a driver cancels, and flag the trip for follow-up.
• Unfulfilled Trips: When a trip ends with no_drivers_available, flag it using the same Get Guest Trip endpoint or webhook.
• Driver Running Late: While there’s no specific webhook, you can check if the trip hasn’t started 10 minutes after the scheduled pickup time and flag it.
• Driver Waiting: If the driver has been waiting for at least 2 minutes, track the trip status to see if it’s still in the arriving state after 2 minutes.
• Delayed Match: If it’s taking more than 5 minutes to find a driver, use the processing status to flag this trip.