DELETE /requests/current
¶ Ride Request - Current
The Ride Request endpoint allows cancellation of the user’s 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.
See the Ride Request tutorial for a step-by-step guide to requesting rides on behalf of an Uber user. Please review the sandbox documentation on how to develop and test against these endpoints without making real-world Ride Requests and being charged.
¶ Resource
DELETE /v1.2/requests/current
¶ Authorization
OAuth 2.0 user access token with the request
scope.
¶ Query Parameters
None
¶ Example Request
curl -H 'Authorization: Bearer <TOKEN>' \
-H 'Accept-Language: en_US' \
-H 'Content-Type: application/json' \
-X DELETE \
'https://api.uber.com/v1.2/requests/current'
¶ Response
Status-Code: 204 No Content
¶ HTTP Error Codes
Below is a list of the HTTP error codes this endpoint could return.
HTTP Status | Code | Description |
---|---|---|
403 | forbidden | Forbidden |
403 | cancel_cash_trip_not_allowed | Trips using the cash payment method must be canceled by the driver. |
404 | no_current_trip | User is not currently on a trip. |