Three lines

Uber

Developers

PATCH /requests/current

Privileged Scope This endpoint requires a privileged scope to be used in production by all Uber riders. You can use this endpoint immediately when authenticated as yourself or any of your 5 registered developers. When you are ready to distribute your application broadly for use by all Uber riders, you may request FULL ACCESS. For more information read about scopes.

Ride Request - Current

The Ride Request endpoint allows updating an ongoing request’s 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.

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

PATCH /v1.2/requests/current

Authorization

OAuth 2.0 user access token with the request scope.

Patch Parameters
Name Type Description
end_latitude (optional) float The final or destination latitude. Either this or end_place_id must be specified.
end_longitude (optional) float The final or destination latitude. Either this or end_place_id must be specified.
end_address (optional) string The final or destination address.
end_nickname (optional) string The final or destination nickname label.
end_place_id (optional) string The final or destination place ID. This is the name of an Uber saved place. Only “home” or “work” is accepted. Either this or end_latitude and end_longitude must be specified.
Example Request
curl -H 'Authorization: Bearer <TOKEN>' \
     -H 'Accept-Language: en_US' \
     -H 'Content-Type: application/json' \
     -X PATCH \
     'https://api.uber.com/v1.2/requests/current'
Response

Status-Code: 204 No Content

Error Responses
Error Code Description
401 unauthorized Invalid OAuth 2.0 credentials provided.
403 forbidden Forbidden. This may occur if the trip was requested from a source that’s different from your app.
404 no_current_trip User is not currently on a trip.
422 validation_failed The input failed invalidation. This may happen if any of the input fields failed validation. For example, latitude and longitude fields need to be updated at the same time.

Uber

Developers
© 2023 Uber Technologies Inc.