The Applications API manages the full pipeline between job seekers and recruiters. Job seekers can submit an application with a cover letter and salary expectation, track all the roles they have applied to, and withdraw if needed. Recruiters can view every applicant for a specific job listing and move candidates through the hiring pipeline by updating their status. 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.
GET /api/v1/applications/applylist
Returns every application submitted by the authenticated user, joined with the corresponding job details and company name.Requires authentication (
token cookie).POST /api/v1/applications/:id/apply
Submits a new application for the job identified by:id. Each user may apply to a given job only once; a duplicate attempt returns 401.
Requires authentication and the
guest (job seeker) role. The :id in the path is the job UUID.UUID of the job being applied to.
Covering letter text. 10–250 characters.
Availability in days (0–90).
Expected annual salary. 5,000–10,000,000.
Why the applicant should be hired. 10–250 characters.
DELETE /api/v1/applications/:id/withdraw
Withdraws the authenticated user’s application for the job identified by:id. If no matching application exists the request succeeds silently.
Requires authentication. The
:id in the path is the job UUID (not the application UUID).UUID of the job whose application should be withdrawn.
GET /api/v1/applications/:id/applist
Returns all applicants for the job identified by:id. Each row includes the applicant’s contact details, skills, resume URL, and current status.
Requires authentication, the company-employee role, and ownership of the job (i.e. the job must belong to the caller’s company).
UUID of the job whose applicant list is being retrieved.
POST /api/v1/applications/:id/status
Changes the hiring-pipeline status for a specific applicant on a specific job. Both the job UUID (:id path param) and the applicant’s user UUID (user_id body field) must be provided.
Requires authentication and the company-employee role. The
:id in the path is the job UUID.UUID of the job.
UUID of the applicant whose status is being changed.
New status. Allowed values:
applied, shortlisted, rejected, hired.