The journey to upfront fares

Today, we are launching support for upfront fares for all of our Riders API v1.2 endpoints. Upfront fares makes it clear for riders to know how much their trip will cost before they request. Upfront fares are now enabled in the API for Uber products that support upfront fares. With the move to upfront fares, the destination is now required and the fare for the trip must be shown to the user before the ride is requested. As part of this step forward, we are also announcing the availability of upfront fares in the Ride Request Widget.

Deprecating rate limit headers

With the introduction of the Riders API v1.2, we are removing support for rate-limiting headers. In the next few months, we will introduce a new endpoint to query for real-time rate-limiting status for a given endpoint. We are also working on being more proactive with developers that approach the rate limits. Once an application starts to approach the rate limit, our Developer Platform team will reach out to understand the use case and make sure developers have the capacity to be successful. Find out more in the Rate Limiting guide.

Deprecating Riders API v1.0 + v1.1

We will follow up with detailed deprecation plans and the official end of life date for the Riders API 1.0 + 1.1 endpoints in Q1. We plan to deprecate the 1.0 + 1.1 endpoints by Q3 2017 and will work with the community to ensure a seamless migration to v1.2. Developers working on an integration today should start by using the Riders API v1.2.