Skip to main content
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: Each notification object contains a 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.
Example response

Mark a notification as read

Mark a single notification as read by supplying its id as a path parameter.
Response

Mark all notifications as read

Mark every unread notification in your account as read in a single call.
Response

Send a test notification

Trigger a test in-app notification to verify that your notification integration is working correctly.
Response
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.