---
title: "List job applicants"
method: POST
path: "/v1/{account_id}/jobs/{job_id}/applicants"
tags: ["Jobs"]
---

# List job applicants

`POST /v1/{account_id}/jobs/{job_id}/applicants`

## Request

- Base URL: `https://api.curviate.com`
- URL: `https://api.curviate.com/v1/{account_id}/jobs/{job_id}/applicants`
- Auth: HTTP bearer

Lists applicants for a classic job posting the connected account owns. This is a read, POST is used to carry the filter body, matching the /v1/search/* convention; nothing is mutated. Omit `ratings` to see the full applicant funnel; the server sends all four rating values by default.

## Path parameters

- `account_id` string, required
- `job_id` string, required

## Query parameters

- `limit` integer
- `cursor` string

## Request body

- object
  - `ratings` string[]: Filter by applicant rating. Omit to see the full funnel: the server sends all four ratings by default so the total matches the posting's own applicant count.
  - `keywords` string: Free-text keyword filter over applicant profiles.
  - `sort_by` 'APPLIED_DATE' | 'FIRST_NAME' | 'LAST_NAME': Sort order for the returned applicants. Defaults to APPLIED_DATE.
  - `location` string[]: Location parameter ids from GET /v1/{account_id}/search/parameters.
  - `years_of_experience` object[]: Years-of-experience ranges to filter applicants by.
    - `min` integer
    - `max` integer
  - `skills` string[]: Skill parameter ids from GET /v1/{account_id}/search/parameters.

## Response `200`

Applicants matching the filter. Omitting `ratings` requests all four values, so the default view reflects the posting's whole applicant funnel. Content fields (profile, screening-question answers) are returned verbatim and are never stored.

- object
  - `object` 'job_applicant_list', required: Response type discriminator.
  - `items` object[], required: Applicants matching the filter.
    - `object` 'job_applicant', required: Response type discriminator.
    - `id` string, required: The applicant's numeric identifier.
    - `messaging_token` string, required: Opaque token, pass it to start a chat with this applicant.
    - `applied_at` string, required: ISO-8601 UTC timestamp the applicant applied.
    - `viewed_at` string: ISO-8601 UTC timestamp this applicant was viewed, when set.
    - `last_messaged_at` string: ISO-8601 UTC timestamp last messaged, when set.
    - `profile` object, required: The applicant's profile (content pass-through, never stored).
      - `id` string: The profile's identifier.
      - `display_name` string: The applicant's display name.
      - `headline` string: The applicant's headline, when set.
      - `location` string: The applicant's location, when set.
      - `network_distance` string: Network distance to the connected account.
      - `profile_url` string: The applicant's public LinkedIn profile URL, when set.
      - `public_identifier` string: The applicant's vanity slug, when set.
      - `public_picture_url` string: The applicant's public picture URL, when set.
    - `rating` 'UNRATED' | 'NOT_A_FIT' | 'MAYBE' | 'GOOD_FIT' | 'null', nullable, required: This applicant's rating, or null when not yet rated.
    - `screening_questions` object[], required: Screening questions and this applicant's answers, when the posting has any.
      - `question` string: The screening question text (content pass-through, never stored).
      - `has_succeeded` boolean: Whether this applicant's answer met the question's bar.
      - `is_eliminatory` boolean: Whether failing this question disqualifies the applicant.
      - `answers` string[]: The applicant's answer(s) (content pass-through, never stored).
  - `paging` object, required
    - `total_count` number, required: Total applicants matching the requested filter (post-filter, omitting `ratings` requests all four values, so this reflects the posting's whole applicant funnel by default).
  - `cursor` string: Opaque pagination cursor for the next page. Present only when more applicants remain past this page, omit on the first request, pass back verbatim to page forward.
  - `safety_warning` SafetyWarning: Present on a successful response when this account crossed an account-safety ceiling while the affected budget row is on the default warn posture. The action still happened. Field-identical to the BUDGET_EXHAUSTED error body except that blocked is false and hint.message describes the outcome, so one branch handles both postures and switching the account to enforce is a configuration change rather than a client rewrite.
    - `row` string, nullable, required: The budget row that breached, for example profile_views or pending_invites. Null when the breach is not about a row: an activity_window warning on an action that spends no budget of its own (editing a message, dismissing a notification, a Recruiter or Sales Navigator admin action) is still governed by the hours the account works in. Read hint.parameter for what to change; whenever this is null it names posture, because the activity window edges are set per action type and this action has none, so the levers that reach it are the account timezone and posture.
    - `reset_at` string, nullable, required: The instant the refusal lifts: the window roll on a ceiling refusal, the next window open on an activity-window one. Null in the two cases no clock frees, the pending_invites gauge and InMail credits (row inmail).
    - `hint` object, required
      - `parameter` string, required: The settable parameter on PATCH /v1/{account_id}/safety-policy.
      - `message` string, required: What the condition is and what changing that parameter would do. This is the one field whose text differs from the BUDGET_EXHAUSTED refusal: here it says the action went through, and on a ceiling breach how far past the ceiling this row now stands, rather than telling you to set posture to warn when it already is. Branch on parameter, reason and blocked, never on this text.
    - `reason` 'ceiling' | 'activity_window', required: Which rule was crossed. ceiling means the row's configured limit is spent; activity_window means the account is outside the hours it works in, which is a different fact with a different remedy. hint.parameter names the right setting for each.
    - `blocked` boolean, required: Always false here. True on the BUDGET_EXHAUSTED refusal carrying the same payload.

## Other responses

- `400`: Invalid filter body, limit greater than 100, or malformed cursor.
- `401`: Missing or invalid API key.
- `403`: Forbidden. NO_ACTIVE_SEAT: the account is not attached to an active seat.
- `404`: The account_id does not belong to this tenant, or the job posting was not found. An id whose connection was replaced or removed also stops resolving here, and it is already absent from the list, so re-read `GET /v1/accounts` for the current id.
- `413`: Payload too large, the request body exceeds the size limit.
- `422`: The account is restricted and cannot be queried.
- `429`: Rate limited, slow down and retry after the hinted delay.
- `500`: Internal error.
- `502`: A temporary error occurred. Please try again.
- `503`: Service unavailable.
- `504`: Gateway timeout.

---

[API](https://skmtc.dev/curviate/apis/curviate-api.md) · [All operations](https://skmtc.dev/curviate/apis/curviate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/curviate/apis/curviate-api/revisions/eab848801d95?raw)