Yesterday we announced an exciting new feature for developers — Uber Trip Experiences.

In addition we are also releasing a series of refinements, updates and great new endpoints to the API to make it even easier for you to build moving experiences. As always, users must give permission before any app can connect to Uber and access their trip details.

Trip Experiences (/requests/current + all_trips Scope)

This new endpoint allows developers to more easily access details about rides they initiate with the Ride Request endpoint. With our new all_trips privileged scope, developers can also access trip details for every trip a user takes to unlock unique features whenever users are on a trip with Uber. Learn more.

Places

With our new /places endpoint, developers can get and update a user’s saved Home and Work address and use these pre-saved addresses when requesting a ride via the Ride Request API. This is available to developers via a new ‘Places’ scope. Learn more.

Optional Destination

Sometimes users won’t know exactly where they want to go when requesting a ride. Now developers can request a ride without specifying a destination. Learn more.

Destination Updates

Sometimes users change their mind while on-trip. Developers can now update the destination while on trip. Learn more.

Default Product

To date, using the Ride Request endpoint has typically required the use of our /products endpoint so an app can, for each trip and for each location, specify the unique Product ID to be used. Often times, however, you just want to get your users moving with UberX or equivalent. Now you can, by leaving the Product ID blank in the Ride Request and we’ll automatically find the best, most cost-effective option. Learn more.

Payment Method

With the new /payment-methods endpoint and scope, developers can now get a list of Payment methods on file with Uber (e.g. “Visa ending in 1234”) so that users can select how they want to pay for their ride from within a 3rd party app. Learn more.

SMS Verify

Traditionally, new users have to download the Uber App to verify their mobile number. For some apps or use-cases, this can be cumbersome for onboarding new users and getting them moving quickly. Whitelisted developers can now switch to SMS verification. This modifies the Uber signup process slightly so that users can verify their mobile phone number with a simple link sent via a text message. Learn more.


The Journey Continues

With these updates to the API we hope that now more than ever developers have the tools they need to build moving experiences. We’ll continue to add more features as time goes on and we can’t wait to see what you come up with next!

To get updates from the Uber Developer team in the future, follow our publication on Medium or follow us on Twitter.

Comments