Does Uber provide API to access Scooter and bike data? - uber-api

I am integrating JUMP scooters in my application. Till now I was using gbfs urls to get the bike status, pricing etc. After JUMP was acquired by Uber gbfs urls do not work anymore. Uber because of the privacy & data securit policy are not posting the data to gbfs anymore
Does Uber provide API to access Scooter and bike data ?
Can somebody help
I am trying WoBike/JUMP.md but it is tedious process. Still havent been able to get it

Related

Uber Central API

Trying to find concrete information regarding whether or not you can request rides for other people using an Uber Central API. I want to be able to offer clients that come to my business a ride home or a ride to my business. I see Uber Central is meant to fill that, but is there a way to use the API to do what Uber Central is made to do?
Specifically, is there an Uber Central API available yet?
I can confirm there is not an Uber Central API available.

Uber API: API method/CVS sheet to get full rides info for each rider in the company

We have an Uber company-level account with a lot of autos working in the Uber application (~ 50-100 depends on several cases).
Now we are building analytic app, that aggregates information about each car earnings/rides for each our driver.
Do we need to get "Uber for Business" to get aggregated information for each driver/rides from https://developer.uber.com/docs/businesses/data-automation/data-download, or we need to build application, where each our rider needs to authorize to grant access to its information with bearer token, and iterate over each token on endpoints https://developer.uber.com/docs/drivers/references/api/v1/partners-payments-get and https://developer.uber.com/docs/drivers/references/api/v1/partners-trips-get?
I think, that last method is the crooked nail for us.

Will the Ride Request Widget deprecation affect the REST API Uber exposes?

I've recently seen this message:
This product is deprecated and will no longer be supported on May 31st, 2018. If you are starting a new project you should use deep links to m.uber.com. See the migration guide on how to link to the latest Uber rider experience.
Here's a screenshot of this message
Keeping in mind that this widget offers these functionalities(as does the REST API):
Selecting a service (e.g., uberX, UberBlack, etc.)
Specifying pickup and dropoff locations
Viewing time and price estimates
Requesting a ride
Will the Rest API be somehow affected by this change?
Will I be able to further make requests like these ones?
GET /v1.2/estimates/price
GET /v1.2/history
GET /v1.2/places/{place_id}
I'm not an Uber representative, and I really kind of feel that asking support from a vendor is the way to go for a vendor specific thing. However, when I read that message and screenshot they are clearly talking about a widget, not a REST api.

Uber API to detect rides

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

Is there functionality to request an Uber on another person's behalf?

My business opportunity would benefit from being able to request an Uber to pick up a client and arrive at my place of business, and not just the client requesting the Uber themselves. Is this something that I can do today with Uber?
edit: the origin of my request would be different than the requested pick-up location.
The Uber API gives you the ability to Request an Uber Product on behalf of users within your application. Given you know where a user currently is, where they want to go, and which Uber product they want to use to get there, you have all of the tools to make that happen with a few simple API endpoints.
Looks like I answered my own question :)