# /usajobs/jobs

`POST /api/usajobs/jobs`

Price: 5 credits

Get one US federal job announcement from USAJOBS by its control number. Returns the full announcement: title, department, agency and hiring organization, summary, duties, requirements (conditions of employment, qualifications, education), how applicants are evaluated, required documents, how to apply and the next steps of the hiring process, plus the overview metadata — application status, posting and closing dates, duty locations with vacancy counts, salary, pay scale and grade, promotion potential, work schedule, appointment type, travel, supervisory status, telework and remote eligibility, relocation, drug test, financial disclosure, union representation, federal service type, security clearance and position sensitivity — together with the hiring paths the job is open to and the agency contact details.

## How to use it

Fetch a single USAJOBS federal job announcement. Pass job as the 9-digit control number (for example 875781800) or the full announcement URL — both are accepted. Control numbers come from the id field of the USAJOBS job search endpoint. Federal announcements close on a fixed date and are removed afterwards, so a control number that worked before can later return 412. The response contains the complete announcement text (summary, duties, requirements, evaluation, required documents, how to apply) plus structured overview fields and the agency contact.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `job` (string, required) — Job control number or the URL of the announcement (examples: "875781800", "https://www.usajobs.gov/job/875781800")

## Response

### 200 — Successful Response

- `@type` (string) (default: "UsajobsJob")
- `id` (string, required)
- `announcement_number` (string, nullable)
- `job_title` (string, nullable)
- `url` (string, nullable)
- `department` (string, nullable)
- `agency` (string, nullable)
- `hiring_organization` (string, nullable)
- `application_status` (string, nullable)
- `posted_display` (string, nullable)
- `close_date_display` (string, nullable)
- `vacancy_display` (string, nullable)
- `locations` (array) (default: [])
  - `@type` (string) (default: "UsajobsJobLocation")
  - `name` (string, required)
  - `vacancy_count` (integer, nullable)
- `summary` (string, nullable)
- `duties` (string, nullable)
- `requirements` (string, nullable)
- `evaluation` (string, nullable)
- `required_documents` (string, nullable)
- `how_to_apply` (string, nullable)
- `next_steps` (string, nullable)
- `salary` (string, nullable)
- `pay_scale_and_grade` (string, nullable)
- `promotion_potential` (string, nullable)
- `work_schedule` (string, nullable)
- `appointment_type` (string, nullable)
- `travel_required` (string, nullable)
- `is_supervisory` (boolean, nullable)
- `is_telework_eligible` (boolean, nullable)
- `is_remote` (boolean, nullable)
- `is_relocation_reimbursed` (boolean, nullable)
- `is_drug_test_required` (boolean, nullable)
- `is_financial_disclosure_required` (boolean, nullable)
- `is_union_represented` (boolean, nullable)
- `federal_service_type` (string, nullable)
- `security_clearance` (string, nullable)
- `position_sensitivity` (string, nullable)
- `hiring_paths` (array) (default: [])
  - `@type` (string) (default: "UsajobsJobHiringPath")
  - `code` (string, required)
  - `name` (string, nullable)
  - `description` (string, nullable)
- `contact` (object, nullable)
  - `@type` (string) (default: "UsajobsJobContact")
  - `name` (string, nullable)
  - `phone` (string, nullable)
  - `fax` (string, nullable)
  - `email` (string, nullable)
  - `website_url` (string, nullable)
  - `address` (string, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.

### 412

The announcement does not exist or has been removed from USAJOBS

What to do: Retrying will not help: either the entity does not exist, or the input points at a different one.

### 429

Too many requests: a rate limit or a usage window is exhausted

What to do: When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.

### 500

Something broke on our side

What to do: Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.

### 529

Rate limit reached, or the endpoint is overloaded

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these headers:

- `X-Error` — Error message text (present only on error)
- `X-Request-ID` — Unique request identifier
- `X-Execution-Time` — Execution time in seconds
- `X-Result-Count` — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
- `X-Total-Available-Results` — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
- `X-Warning` — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
- `X-Retry-After` — Seconds to wait before retrying. Present only on 429.