Cancel Ride

Cancel a ride by its ID. The server records the reason, the identity of who cancelled, and any applicable cancellation fee, then returns the updated ride object. Authentication required — include Authorization: Bearer <token> in the request header.

Request

POST /rides/cancel/{rideId}

number

required

The unique ID of the ride to cancel.

string

An optional explanation for the cancellation. Stored in cancellationReason on the ride.

Response

number

Unique ride identifier.

string

Always CANCELLED after a successful cancellation.

string

The reason provided in the request body, or an empty string if none was given.

string

Identifier indicating who initiated the cancellation (rider or driver).

number

Fee charged for the cancellation, or null if no fee applies.

number

ID of the rider.

number

ID of the assigned driver, or null.

number

Original fare for the ride.

string

Pickup address.

string

Drop-off address.

string

ISO 8601 timestamp of ride creation.

Example

curl -X POST "http://localhost:8080/rides/cancel/1021" \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "reason": "Driver is taking too long"
  }'

{
  "id": 1021,
  "status": "CANCELLED",
  "riderId": 42,
  "driverId": 7,
  "fare": 145.00,
  "pickupLocation": "MG Road, Bangalore",
  "dropLocation": "Indiranagar, Bangalore",
  "cancellationReason": "Driver is taking too long",
  "cancelledBy": "rider",
  "cancellationFee": 25.00,
  "createdAt": "2026-04-02T10:15:30Z"
}

A cancellationFee may be charged depending on how much time has elapsed since the ride was accepted. Check the cancellationFee field in the response to see the exact amount deducted.

You can send a cancellation request with no body — the reason field is entirely optional. If you omit the body, the cancellationReason on the ride will be stored as an empty string.

Authentication

Rides

Payments

Notifications & Settings

Request

Response

Example

​Request

​Response

​Example

Request

Response

Example