uberPOOL, now available in the Uber API
uberPOOL is one of Uber’s fastest-growing services, with over 100,000 people taking pooled trips every week in cities including San Francisco, New York, Los Angeles, Beijing and Bangalore. As more and more Uber riders choose to carpool, we want to make sure that developers have access to this product in their apps. Starting today, uberPOOL is now available through the Uber API.
If your application uses the Uber Rides API, uberPOOL will begin to show as an available product in certain API endpoints. With the caveat of requiring a destination at POST /v1/requests, the normal ride request flow will work for your users. For your reference, these are the endpoints which will begin to handle uberPOOL specific parameters and fields:
- GET /v1/products — the response will now include uberPOOL products, which can be identified with having “shared”: true.
- GET /v1/estimates/price and GET /v1/estimates/time — the response will now include uberPOOL products.
- POST /v1/requests/estimate — the request may contain a seat_count parameter and the response will contain a fare_id field.
- POST /v1/requests — the request may contain seat_count and fare_id parameters for the uberPOOL ride. Destination is required when creating a request for uberPOOL products.
- GET /v1/requests/{request_id} and GET /v1/requests/current — the response body has riders and waypoints fields that contain additional details about the trip.
We encourage you to read through the uberPOOL documentation and try out uberPOOL in your app to make sure it’s a great experience for your users. You can also take advantage of some of the more advanced integration options, such as specifying seats required in the car.
This change is part of our continued commitment to bringing the full power of Uber to our developer community everywhere.
⚀ To get updates from the Uber Developer team in the future, follow our publication or follow us on Twitter.
⚀ Please tap or click “♥︎” to help to promote this piece to others.
