The Notifications API delivers real-time alerts to Yeti Jobs users — including new job matches, application status changes, company-follow confirmations, and platform announcements. Each notification is linked to the user who receives it and optionally to a specific job or company. The API supports fetching the full notification feed, toggling read/unread status on individual notifications, bulk-marking all as read, and programmatically sending a notification to any user by UUID. All endpoints require a validDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/tech-dipesh/yeti-Jobs/llms.txt
Use this file to discover all available pages before exploring further.
token cookie.
Supported notification types: new_jobs, application_status, job_alert, bookmark_reminder, company_follow, application_recieved, profile_view, message_recieved, resume_analysed, announcement.
GET /api/v1/notifications/all
Returns all notifications for the authenticated user, ordered newest-first. Each item includes the resolved job title and company name from joined tables.Requires authentication (
token cookie).Notification UUID.
Notification type. One of:
new_jobs, application_status, job_alert, bookmark_reminder, company_follow, application_recieved, profile_view, message_recieved, resume_analysed, announcement.ISO 8601 timestamp of when the notification was created.
ISO 8601 timestamp of when the notification was read, or
null if unread.UUID of the associated job, or
null.UUID of the associated company, or
null.UUID of the notification recipient.
Title of the associated job (joined from the
jobs table), or null.Name of the associated company (joined from the
companies table), or null.PATCH /api/v1/notifications/read-all
Marks every notification belonging to the authenticated user as read by settingread_at to the current timestamp.
Requires authentication.
POST /api/v1/notifications/:id
Sends a new notification to the user identified by:id. The notification is stored in the database and associated with the caller’s session. Both job_id and company_id must be valid UUIDs that exist in the system.
Requires authentication. The
:id in the path is the recipient user’s UUID.UUID of the user who will receive the notification.
Notification type. Must be one of:
new_jobs, application_status, job_alert, bookmark_reminder, company_follow, application_recieved, profile_view, message_recieved, resume_analysed, announcement.UUID of the related job.
UUID of the related company.
PATCH /api/v1/notifications/:id/read
Toggles the read state of a single notification. Pass?isRead=true to mark it as read (sets read_at to current_timestamp) or ?isRead=false to mark it as unread (clears read_at). The notification must belong to the authenticated user.
Requires authentication. The
:id in the path is the notification UUID.UUID of the notification to update.
true to mark the notification as read; false to mark it as unread. Defaults to true.