There is no option in uber api documentation to schedule rides for future.
But the following products provide Uber pre-booking:
https://www.ridesharp.co/
https://www.trykommen.com/
How is this possible?
They are just providing their own mechanism to 'schedule' a ride. All they are doing is storing the time & details for the request and then making the request call at the appointed time. There is no scheduled ride API.
Related
I want to know whether I can use uber api to track the ride real-time basis. I have found uber help suggest the following:
"Can I see the path a rider took during a trip?"
This feature is only available for ongoing UberPOOL rides. The request details return a set of waypoints (incl. pickup and dropoff locations) for each UberPOOL ride. This information is not accessible in the history but just during the ride.
So does it mean it is not applicable to other types of ride? Please let me know. It will be great if someone can suggest exact API endpoint for tracking the ride on a real-time basis.
Thanks.
It can be checked for any type of ride that you've requested
The Ride Request endpoint allows retrieving the status of an ongoing or completed trip that was created by your app
You have a few different options
Ride Request - Map API
Ride Request - Current API
Ride Request - Details API
Is it possible to use the Uber API to detect rides that originated from the Uber app?
I'm trying to get a machine learning system to learn when you are using uber.
No, whether a ride originated from the Uber app or from a separate integration is not a field/endpoint in the current Uber API.
Not sure if this is exactly what you are looking for but something that might be helpful is the /history endpoint. "The User Activity endpoint returns a limited amount of data about a user’s lifetime activity with Uber. The response will include pickup and dropoff times, the city the trips took place in, the distance of past requests, and information about which products were requested."
Documentation: https://developer.uber.com/docs/riders/references/api/v1.2/history-get
I am trying to build a process to consume history api of Uber to display details of the users trips on one of my webpage. Has anyone done this?
I see that api definition on the UBER site
https://developer.uber.com/docs/rides/api/v12-history
However this does not provide how to provide the driver id? How can i get to the history of one particular driver?
All i need is trip details for every driver - assuming the driver id is available.
Any request sample will actually help.
Uber currently does not have API endpoints that provide information about driver activity. This is something we are considering, but at this time we do not have any public plans for a release.
Thanks for your interest in the Uber API. Follow #Uber_API and visit devblog.uber.com for updates and announcements.
We are busy looking at Uber Ride API and would like to find out the following:
Is all_trips scope applicable if OAuth authorized user is an Uber driver?
Will Webhook invoke events everytime when a driver accepts/cancels/completes a trips?
will Webhook be invoked during a real trip while the app is under development or Only work in Sandbox?
No. The all_trips scope only works for riders.
Yes. Every trip status change triggers a webhook. Possible statuses changes are:
processing
no_drivers_available
accepted
arriving
in_progress
driver_canceled
rider_canceled
completed.
(List pulled from here, according to the webhooks documentation here).
Yes. If you grant your app the all_trips scope, the Uber API will send webhooks to the URL you have registered at developer.uber.com/dashboard for every trip you take, i.e. sandbox and real trips alike. Note that there is currently no way to flag an Uber app as "in development" or "in production".
I have created a Uber app(Rides API) and using server token i can able to get
Price and Time estimates.
How can I schedule a driver using Uber api?
If you want to make a request for a ride, you need to POST to /requests. Like agraebe said, you can find documentation on that endpoint here.
This page also has a tutorial on requesting a ride, and the lifecycle of a request, walking you through step by step how requests work.