[API] Delete Vehicle
The Delete Vehicle is designed for vehicle suppliers managing Fleets or Rental services, enabling them to efficiently remove vehicles that are no longer active or required
¶ Resource
/v1/vehicle-suppliers/vehicles/:vehicle_id
¶ Use Case
The “Delete Vehicle” API ensures that vehicle listings are up-to-date and accurate, facilitating better management and operational clarity. Updates made through this API are reflected in the system, typically within less than 2 minutes, thereby maintaining the integrity and relevance of the vehicle data.
¶ Support for Hierarchical Data
The Delete Vehicle API automatically operates within the hierarchical structure of the organization linked to the developer’s account at the time of setup.
¶ Supported supplier types
Fleets/Rentals
¶ Scopes
vehicle_suppliers.vehicles.write
Resource
/v1/vehicle-suppliers/vehicles/:vehicle_id
¶ HTTP Method
DELETE
¶ Authorization
¶ Example Request
curl -X DELETE "https://api.uber.com/v1/vehicle-suppliers/vehicles/:vehicle_id" \
-H "Authorization: Bearer <TOKEN>" \
-H "Content-Type: application/json"
¶ Request Path Parameters
Name | Type | Description |
---|---|---|
vehicle_id |
string | Vehicle ID returned from Create Vehicle response. |
¶ Example Response
Status-code: 204 No Content
{
}
¶ Response Body parameters
None: No data is returned in the body of the response. This is the expected response when a vehicle is successfully removed.
Rate limit
- The rate limit for this endpoint is 1000 requests per hour (RPH).
¶ Endpoint Specific Errors
Http Status Code | Code | Message |
---|---|---|
400 |
bad_request | The request parameters are invalid |
401 |
unauthorized | Invalid OAuth 2.0 credentials provided |
404 |
vehicle_not_found | The vehicle was not found or not authorized |
429 |
delete_assigned_vehicle | Not allowed to delete the assigned vehicle |
422 |
rate_limited | Number of requests exceeds allowed limit |
500 |
internal_server_error | Internal server error |
503 |
service_unavailable | Service unavailable |