¶ Use case

Use this endpoint to update an employee trip.

The update to Scheduled Rides means that the existing trip will be canceled, and a new one will be initiated using the updated information. However, please note that we do not support updates to reserve trips before they are accepted by a driver.

In order to request a ride for a third party client (3PC), please add x-uber-organizationuuid header and the Organization UUID as the value.

¶ To update an active ride (a trip dispatched to a driver)

Only the destination and intermediate stops can be updated for active rides. You will need to ensure any fields other than the destination and the requested stops are the same as what they were set to when the trip was created. You can call GET /v2/employees/trips/{request_id} to retrieve those fields.

After updating them, subsequent calls to GET /v2/employees/trips/{request_id} will show the latest destination and requested stops updated in the destination and stop fields of the response.

¶ Authorization

OAuth 2.0 Bearer token with the business.trips scope.

¶ Ride Types

                                                                                                                                                                                              |

¶ Request

¶ Example request

Try It

curl -X PUT \
  -H "authorization: Bearer <access_token>" \
  -H 'content-type: application/json' \
  -d '{
        "customer": {
          "customer_type": "EMPLOYEE"
          "email": "jane@example.com"
        },
        "request_id": "42541eb5-8ced-4ed9-af4b-f92359816a23",
        "product_id": "a1111c8c-c720-46c3-8534-2fcdd730040d",
        "pickup": {
          "latitude": 40.750568,
          "longitude": -73.993519
        },
        "dropoff": {
          "latitude": 40.752558,
          "longitude": -74.006469
        },
        "requested_stops": [
          {
            "latitude": 40.7284,
            "longitude": -73.9357
          },
          {
            "latitude": 40.7322,
            "longitude": -73.9682
          }
        ],
        "expense_code": "sample code",
        "expense_memo": "sample memo"
      }' \
      'https://api.uber.com/v2/employees/trips/<trip_uuid>'

When using the sandbox environment, the request requires the x-uber-sandbox-runuuid header with the run_id as the value (e.g, -H "x-uber-sandbox-runuuid:<run_id>").

In order to specify an org for which the ride needs to be billed to, the request requires the x-uber-organizationuuid header with the Org UUID as the value (e.g, -H "x-uber-organizationuuid:<org_UUID>").

¶ Request Query parameters

¶ Request parameters

¶ Response

¶ Example response

{
  "requestID": "b56cd183-5512-4f1a-8f02-ce944b76a117"
}

A successful request will receive a 200 with an empty response with the requestID.

¶ Expected Errors

{
  "code": "validation_failed",
  "data": {
    "invalid_field_changed": "pickup"
  },
  "message": "Only destination can be updated for active rides"
}

{
  "code": "bad_request",
  "message": "The ride that has reached a final state and cannot be updated."
}

{
  "message": "You can only adjust your pickup point within the area shown.",
  "data": {
    "statusCode": "400"
  },
  "errCode": "pickup_cannot_be_updated",
}

{
  "message": "Sorry, you are not eligible for a pickup location change!",
  "data": {
    "statusCode": "400"
  },
  "errCode": "pickup_cannot_be_updated",
}

¶ Internal Server Errors

{
  "message": "Something went wrong - please try again.",
  "data": {
    "statusCode": "500"
  },
  "errCode": "internal_server_error",
}