almost 5 years ago
The wait is officially over and we have some new tools for you all! I’m excited to announce the release of webhooks, estimates, and receipts. Whether you’re still starting your project or have already completed it, there’s always room for improvement. Although these new functionalities are optional for your project, you can bet that we will take notice if you use them. Best of luck and please let us know on the discussion board if you have any questions!
In general, a webhook is a way for an app developer to specify a URL to receive notifications based on some trigger. In the case of Uber, developers that utilize the Request endpoint can now leverage our webhooks service to have their applications notified when certain events happen on behalf of a user they have requested a ride for. You can learn more about our webhooks here.
Introducing Request Estimates
With Request Estimates, developers can make a `POST` to an endpoint and receive time, price, and surge information that can optimize the experience for a user while at the same time reducing the number of requests made to the API. You can learn more about Request Estimates here.
Introducing Receipts and History v1.2
We’ve created a new resource Request Receipts that allows third party applications to surface the cost and details of a Request to users at the end of a trip. This can further enhance the in-app Uber experience for users making requests outside the official Uber apps. Similar to the `request` scope, `request_receipts` is a whitelisted scope that requires approval before being made available to an application.
The History endpoint has also been updated with a new version that now includes a `start_city` object that provides the name, latitude, and longitude of the cities where user activity has taken place in. This endpoint requires the repurposed `history` scope and will require users to re-authorize any applications that have used the `history_lite` scope in the past. You can learn more about Receipts and the History V1.2 endpoint here.
Did you miss out on some of our other announcements?
- Product.price_details and Request.location.bearing: We released two new resource properties for you to use. Learn more here.
- Windows Phone Deep Link: Uber for Windows Phone now accepts deep linking just like iOS and Android apps. Now developers of Windows Phone applications can make it easy for their users to interact with the native Uber app. The URL scheme is the same with all parameters and functionality supported. Learn more here.
P.S. If you’re finished with your project and you want to share it with us, feel free to tweet a link to us @Uber_API.
-Nathan Lam, Product Marketing Lead, API