|Gain A Competitive Edge With Uber's Driver API|
|Written by Nikos Vaggalis|
|Tuesday, 08 November 2016|
A new sort of API, invokable by 3rd party consumers and carrying brand new functionality, finds its way to Uber's repository's already rich collection of APIs and Uber is offering developers beta access.
Until now Uber's repository has contained the purely client-centric APIs of the Ride Requests, Trip Experiences and UberRUSH Deliveries (an API for logistics and on demand delivery that lets customers track the location of their delivery from any device). The new Driver API is different in that it doesn't attempt to enhance a passenger's ride but instead looks at things from a driver's perspective and comprises a set of well defined REST endpoints:
Accessing this endpoint returns the profile of an authenticated driver, complete with name, email, ratings, trip count and activation status.
One potential use of this endpoint is that by presenting the driver's personal details, Uber re-assures the rider of a trustworthy ride. It is crucially concerned with driver reputation, providing statistics such as the driver's ratings and trip count. By going public with such details Uber preferentially rewards a driver over other lower ranked colleagues.
The endpoint is accessible through a GET request (and an OAuth 2.0 token as a header) to https://api.uber.com/v1/partners/me
A typical response from the service is a JSON object filled with the driver's details:
An endpoint that supplies a 10-day flashback of data on the driver's earnings. It's offered as a service for the driver's internal consumption and can be used to keep the driver's transactions under close monitoring and generate payment reports such as breakdowns of income or expected taxes, thus aiding the driver in keeping track of the job's financial aspects.
It is again accessible through a GET request to https://api.uber.com/v1/partners/payments
Typical response is a JSON array whose elements are indexes of unique transactions information:
This endpoint is by far the most interesting, and potentially profitable from a driver's perspective. It is typically to be used by third party driver's partners, concerned with capitalizing on each trip's attached meta-data, so that they can offer services, discounts or loyalty programs to their drivers. Existing examples in Sears offering 50% off oil changes and 30% back in points on all labor at Sears Auto Centers, or in Sherpashare's processing the trip data for generating optimal routes in order to help driver-partners get additional ride requests.
The endpoint is accessible in a similar fashion through
"status": "completed", "duration": 1220, "trip_id": "e33f756b-16e9-4cb4-96d4-ef0d0e5c9838" }] }
As such, the Driver API takes Uber one more step further down the road of its attempts to provide a centralized and integrated platform in the ever competitive ride sharing business, luring even more clients, riders, drivers and developers under one roof.
The only hindrance to the Driver's API widespread adoption is, that, as it currently stands, the API is offered as a limited beta with interested parties having to fill an application in order to be granted access.
or email your comment to: firstname.lastname@example.org
|Last Updated ( Tuesday, 08 November 2016 )|