---
title: "Get job posting"
method: GET
path: "/v1/{account_id}/jobs/{job_id}"
tags: ["Jobs"]
---

# Get job posting

`GET /v1/{account_id}/jobs/{job_id}`

## Request

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

Returns one classic job posting at full detail. Any posting reachable by its numeric id can be retrieved, including one not owned by the connected account. Pass `with_sections` for extra sections.

## Path parameters

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

## Query parameters

- `with_sections` string[]

## Response `200`

The classic job posting's full detail. Content fields (title, description) are returned verbatim and are never stored.

- object
  - `object` 'job_posting', required: Response type discriminator.
  - `id` string, required: The job posting's numeric identifier.
  - `title` string, required: Job title (content pass-through, never stored).
  - `company` object, required: The hiring company.
    - `id` string: The hiring company's numeric identifier.
    - `name` string: The hiring company's display name.
    - `public_picture_url` string: The company's public logo URL, when set.
    - `profile_url` string: The company's public LinkedIn profile URL, when set.
    - `public_identifier` string: The company's vanity slug, when set.
  - `location` string: Job location, when set.
  - `state` 'DRAFT' | 'LISTED' | 'CLOSED' | 'REVIEW' | 'SUSPENDED', required: Posting lifecycle state.
  - `is_repost` boolean, required: Whether this posting is a repost of a prior one.
  - `is_application_limit_reached` boolean, required: Whether this posting has reached its application limit.
  - `industries` string[]: Industries associated with this posting, when set.
  - `created_at` string, required: ISO-8601 UTC timestamp the posting was created.
  - `description` string, required: Full job description text (content pass-through, never stored).
  - `views_count` number: Number of views so far, when tracked.
  - `applications_count` number, required: Number of applicants so far.
  - `screening_questions` unknown[]: Screening questions attached to this posting, when any are set.
    - unknown
  - `workplace_type` 'ON_SITE' | 'HYBRID' | 'REMOTE', required: Workplace arrangement.
  - `employment_status` 'FULL_TIME' | 'PART_TIME' | 'CONTRACT' | 'TEMPORARY' | 'OTHER' | 'VOLUNTEER' | 'INTERNSHIP', required: Employment type.
  - `budget` object: Promotion budget, when this posting has one set.
    - `total` object
      - `amount` number: Total budget amount.
      - `currency` string: ISO-4217 currency code.
    - `daily` object
      - `amount` number: Daily budget amount.
      - `currency` string: ISO-4217 currency code.
  - `published_at` string: ISO-8601 UTC timestamp the posting was published, when set.
  - `expires_at` string: ISO-8601 UTC timestamp the posting expires, when set.
  - `closed_at` string: ISO-8601 UTC timestamp the posting was closed, when set.
  - `listed_at` string: ISO-8601 UTC timestamp the posting was listed, when set.
  - `hiring_team` unknown[]: Hiring team members associated with this posting, when the posting exposes any.
    - unknown
  - `observed_at` string, required: ISO-8601 timestamp for when this data was observed on LinkedIn. On a live fetch this is the time of the fetch; on a stored answer it is when the data was actually seen, not when you asked for it.
  - `source` 'store' | 'live', required: Whether this answer came from Curviate's stored copy or from a fresh LinkedIn fetch. A stored answer costs the connected account nothing and is never surfaced to the person being read. It also carries less: fields Curviate does not retain (message bodies, notes, attachments, third-party contact details) are only ever present on a live fetch. Pass mode=live when you need them.
  - `withdrawn` boolean, required: Whether LinkedIn has told us this resource no longer exists, such as a removed profile. When true, the answer above is the copy Curviate still holds and must not be treated as current. Always present; false is the normal case.
  - `withdrawn_at` string: ISO-8601 timestamp for when a fetch MOST RECENTLY found this resource gone on LinkedIn. Every later fetch that finds it gone again moves it. Present only when withdrawn is true.
  - `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`: Missing or empty account_id.
- `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.
- `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)