List applications

GET /jobs/{jobId}/applications returns applications in one pipeline stage — by default the Applications stage — with triage fields, contact details, resume download URL, and screening Q&A. Requires scope applications:read.

Request

GET /api/v1/jobs/{jobId}/applications?fitment=strong,fair&autoUnlock=true&page=1&pageSize=10

Param	Default	Notes
`stageId`	Applications stage	From List stages. Omit to use the applications stage.
`fitment`	`strong,fair`	Comma-separated: `strong`, `fair`, `weak`. Rows with no AI fitment verdict are always included.
`autoUnlock`	`true`	Unlock locked candidates on the page. Upstream unlock always runs; API unlock quota applies only on the sent stage. `false` returns only already-unlocked applications.
`sort`	`relevance`	`relevance` or `recency`
`page` / `pageSize`	`1` / `10`	Max pageSize 20

Fitment

Alias	Internal value	When to use
`strong`	`strong_fit`	Tight shortlist when the pool is large
`fair`	`maybe_a_fit`	Included in the default
`weak`	`not_a_fit`	Include when the pool is thin

Default strong,fair excludes weak / not-a-fit.

Auto-unlock

With autoUnlock=true (default), every locked candidate on the returned page is unlocked first. Unlocks always run upstream (plan credits, download counts, events). Only the sent stage counts against the workspace API unlock quota — same preflight as Get candidate details when listing sent. If remaining API unlock quota is less than the number of locked candidates on that page, the call returns 429 api_unlock_limit_reached and unlocks nothing. With autoUnlock=false, locked applications are omitted — you only get candidates already unlocked for your workspace. No unlocks are attempted.

Response

{
  "jobId": "…",
  "stages": [
    {
      "stageId": "…",
      "stageType": "candidates",
      "stageName": "Applications",
      "applications": [
        {
          "applicationId": "…",
          "threadId": "…",
          "talentCardId": "…",
          "displayName": "…",
          "email": "…",
          "phone": "…",
          "headline": "…",
          "joiningAvailability": {
            "status": "on_notice_period",
            "noticePeriodEndsOn": "2026-09-01T00:00:00.000Z",
            "canJoinHowSoonDays": null
          },
          "lastSeen": "2026-08-01T12:00:00.000Z",
          "relevance": { "fitment": "strong_fit", "fitmentReason": "…", "shortlistingCriteriaScore": 3 },
          "originalResumeDownloadUrl": "…",
          "screeningQuestions": [],
          "unlockedNow": true
        }
      ]
    }
  ],
  "page": 1,
  "pageSize": 10,
  "totalCount": 12
}

The stages array is shaped so multiple stages can be returned later; today it always contains the one requested stage. threadId (when present) is the conversation for Send a message follow-ups. Do not use Invite to apply again for these candidates.

Typical flow after outreach

Invite candidates for first contact
Later: list applications on the job (default stage) to see who applied
Send a message using threadId for follow-ups
Optionally list stages if you need counts in other pipeline stages

Getting started

Guides

Request

Fitment

Auto-unlock

Response

Typical flow after outreach

​Request

​Fitment

​Auto-unlock

​Response

​Typical flow after outreach

Request

Fitment

Auto-unlock

Response

Typical flow after outreach