GET >> /oauth/authorize >> The Authorize endpoint allows you to redirect a user to the authorization URL for your application.
POST >> /oauth/token >> The Login endpoint allows you to authorize your application and get an access_token using the authorization_code or client_credentials grant. You can also refresh the access_token using the refresh_token grant.
GET >> /history >> The history array in the response will have a maximum length based on the limit parameter. The response value count may exceed limit, therefore subsequent API requests may be necessary.
GET >> /payment-methods >> The Payment Methods endpoint allows retrieving the list of the users available payment methods. These can be leveraged in order to supply a payment_method_id to the POST /requests endpoint.
GET >> /products >> The Products endpoint returns information about the Uber products offered at a given location. The response includes the display name and other details about each product, and lists the products in the proper display order. Some products, such as Uber Eats, are not returned by this endpoint.
GET >> /products/{product_id} >> The Products Detail endpoint returns information about a specific Uber product. The response includes the display name and other details about the product.
GET >> /estimates/price >> The Price Estimates endpoint returns an estimated price range for each product offered at a given location. The price estimate is provided as a formatted string with the full price range and the localized currency symbol.
GET >> /estimates/time >> The Time Estimates endpoint returns ETAs for all products currently available at a given location, with the ETA for each product expressed as integers in seconds. If a product returned from GET /v1.2/products is not returned from this endpoint for a given latitude/longitude pair then there are currently none of that product available to request. We recommend that this endpoint be called every minute to provide the most accurate, up-to-date ETAs.
POST >> /requests/estimate >> The Request Estimate endpoint allows a ride to be estimated given the desired product, start, and end locations. If the pickup ETA is null, there are no cars available even if an estimate may still be given to the user.
GET >> /requests/current >> The Ride Request endpoint allows retrieving real-time details for an ongoing trip. This endpoint behaves similarly to the GET /requests/{request_id} endpoint, except you do not need to provide a request_id. If there is no trip in progress the endpoint will result in a 404 not found error. This endpoint will only work for trips requested through your app unless you have the all_trips scope. By default, only details about trips your app requested will be returned. If your app has all_trips scope, however, trip details will be returned for all trips irrespective of which application initiated them.
PATCH >> /requests/current >> The Ride Request endpoint allows updating an ongoing requests destination. This endpoint behaves similarly to the PATCH /v1.2/requests/{request_id} endpoint, except you do not need to provide a request_id. If there is no trip in progress the endpoint will result in a 404 not found error. This endpoint will only work for trips requested through your app unless you have the all_trips scope.
DELETE >> /requests/current >> The Ride Request endpoint allows cancellation of the users current trip. This endpoint behaves similarly to the DELETE /v1.2/requests/{request_id} endpoint, except you do not need to provide a request_id. If there is no trip in progress the endpoint will result in a 404 not found error. This endpoint will only work for trips requested through your app unless you have the all_trips scope.
GET >> /requests/{request_id}/receipt >> The Ride Request endpoint allows getting the receipt information of the completed request. There may be a delay from when the trip ends and when the receipt is ready. The receipt is only available after the requests.receipt_ready webhook notification is sent. The trip receipt may be adjusted after the requests.receipt_ready webhook is sent as finalized receipts can be delayed.
GET >> /requests/{request_id}/map >> The Ride Request endpoint getting a map with a visual representation of a Request.
GET >> /requests/{request_id}/receipt >> The Ride Request endpoint allows getting the receipt information of the completed request. There may be a delay from when the trip ends and when the receipt is ready. The receipt is only available after the requests.receipt_ready webhook notification is sent. The trip receipt may be adjusted after the requests.receipt_ready webhook is sent as finalized receipts can be delayed.