Change Log
2018-02-15
- Announced deprecation of Ride Request Widget to migrate to deep links using m.uber.com
- Announced deprecation of /v1 + /v1.1 endpoints to migrate to v1.2 endpoints
- Privatized Trip Experiences + Deliveries APIs
2017-02-05
- Deprecated private APIs for Ride Reminders
- Deprecated private APIs for Account Creation
2017-06-13
- Calls to GET /me are now possible with any valid access token. The response will contain only a user ID. No user details will be returned apart from the ID.
2016-11-11
- Webhooks for state
accepted
can now occur multiple times due to trip swap feature.
2016-11-03
- Released /v1.2/* endpoints
- Made destination (either
end_latitude
andend_longitude
, orend_place_id
) required for all products. Forupfront_fare_enabled
products, a validfare_id
is now required. - Added new key
upfront_fare_enabled
to indicate that the product supports upfront pricing for GET /products - Deprecated price_details (time, distance, tolls breakdown) if the product has
upfront_fare_enabled
. - Deprecation of
surge_multiplier
andminimum
if product hasupfront_fare_enabled
. Note that products will return an estimate range (“$23-29”) rather than a flat fare (“$25.87”) since can not guarantee an upfront fare through GET /v1.2/estimates/price. - Introducing an entirely new schema style, which will return one of two options. Return an fare object for
upfront_fare_enabled
products. Return an estimate object for anything else in POST /v1.2/requests/estimate - Deprecated
surge_multiplier
and top-leveleta
key completely from GET /v1.2/request/current - Deprecation of the
charges
array and thesurge_charge information
in GET /v1.2/requests/{request_id}/receipt. Removed thenormal_fare
key, which is the summation of the numbers from the now-defunct charges array, for all products.
2016-06-03
- Added
fare_breakdown
key to POST /v1/requests/estimate response
2016-05-26
- Added uberPOOL / shared rides support
- Added
shared
key to GET /v1/products response - Added
seat_count
parameter for uberPOOL ride estimates (POST /v1/requests/estimate) - Added
fare_id
key to uberPOOL ride estimate responses (POST /v1/requests/estimate) - Added
fare_id
andseat_count
parameters for uberPOOL ride requests (POST /v1/requests) - Added
riders
andwaypoints
keys to trip details response for uberPOOL trips (GET /v1/requests/{request_id} and GET /v1/requests/current)
2016-05-12
- Added
product_id
key to the responses for POST /v1/requests, GET /v1/requests/{request_id}, and GET /v1/requests/current
2016-05-03
- Added
expense_code
andexpense_memo
as optional request fields to the POST /v1/requests endpoint.
2016-03-28
- Added
multiplier
andexpires_at
keys to the 409surge
response to the POST /v1/requests endpoint.
2016-03-10
- Added
all_trips.status_changed
webhooks event type to Webhooks page.
2016-01-16
- Changed scope for GET /v1/payment-methods from payment_methods_readonly to request
2016-01-12
- Released /v1/places endpoints
- Released /v1/payment-methods endpoints
- Released /v1/requests/current endpoint
- Released PATCH /v1/requests/{request_id} endpoint.
- Released SMS verification
- Updated /v1/requests to allow optional destinations and optional product parameters
- Updated FAQ
- Updated Terms of Use
2015-09-24
- Released API in China
2015-06-22
- Fixed typo where the
surge
error code was incorrectly documented assurge_confirmation
for theRequest
endpoint
2015-06-02
- Added all possible errors returned by
Request
endpoint
2015-04-21
- Released Request - Estimate endpoint
- Released Request - Receipt endpoint
- Released User Activity v1.2 endpoint
- Launched Webhooks
2015-04-15
- Windows Phone deep linking support launched
2015-04-14
- Updated Design Guidelines and assets
2015-04-03
fare_details
added to Products Types endpointlocation.bearing
added to Request - Details endpoint
2015-03-17
- Released Request endpoints
- Introduce the Sandbox
- Added Request Tutorial to documentation
- Updated Design Guidelines
2015-03-13
- Deprecated /v1/history endpoint
2015-11-17
- Launched the Developer Blog
2014-11-06
- Released Promotions endpoint
2014-09-12
- Released /v1.1/history endpoint
2014-08-20
- Initial release