All notification endpoints require an
Authorization header with a valid bearer token. The API returns only notifications belonging to your authenticated account.Notification events
The RideShare API generates in-app notifications automatically as your ride moves through its lifecycle. Common event types you can expect to receive include:eventType | When it fires |
|---|---|
RIDE_REQUESTED | Your ride booking is confirmed and awaiting a driver |
RIDE_ACCEPTED | A driver has accepted your ride |
DRIVER_NEARBY | Your driver is approaching the pickup point |
RIDE_STARTED | The trip has begun (status changed to PICKED) |
RIDE_COMPLETED | The trip has ended |
RIDE_CANCELLED | The ride was cancelled by either party |
PAYMENT_CONFIRMED | Payment has been processed successfully |
channel (e.g. IN_APP), a human-readable title and message, and a read flag.
Fetch notification history
Retrieve all notifications for your account, including unread and previously read items.Mark a notification as read
Mark a single notification as read by supplying itsid as a path parameter.
Mark all notifications as read
Mark every unread notification in your account as read in a single call.Send a test notification
Trigger a test in-app notification to verify that your notification integration is working correctly.The test notification is queued asynchronously. Call
GET /notifications/history a moment later to confirm delivery. Use this endpoint during development only — it does not correspond to a real ride event.