# /usajobs/events/search

`POST /api/usajobs/events/search`

Price: 5 credits

Search upcoming US federal hiring and recruitment events listed on USAJOBS. Filter by event type (hiring or recruitment event, informational session, resume writing or interview training), online versus in-person, the hiring paths the event is aimed at, and the hosting agency. Each event carries its id, title, URL, date and time with timezone, venue and address (or online flag), registration website, full description, hosting organization, hiring-path badges and the related job announcements promoted at the event.

## How to use it

List USAJOBS federal hiring events — job fairs, recruitment open houses, informational webinars and resume or interview training sessions run by US federal agencies. Filter with event_type (hiring, informational, resume_or_interview_training), is_online, hiring_path (vet, mspouse, student, public and so on) and agency codes; count is how many events to return. Each event exposes id — pass it to the USAJOBS event get-by-id endpoint for the same record, or to the event jobs endpoint for just the related job announcements. Events are unique to USAJOBS and are not aggregated anywhere else.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `event_type` (array, nullable) — Type of hiring event (multi-select) (one of: "7", "8", "9")
- `is_online` (boolean, nullable) — Only online events, or only in-person ones
- `hiring_path` (array, nullable) — Who the event is aimed at (multi-select) (one of: "public", "fed-competitive", "fed-excepted", "fed-internal-search", "fed-transition", "land", "vet", "mspouse", "nguard", "student", "graduates", "ses", "disability", "overseas", "native", "peace", "special-authorities")
- `agency` (array, nullable) — Agency codes hosting the event (examples: ["VA","AR"])
- `count` (integer, required) — Max number of events to return (min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "UsajobsEvent")
- `id` (string, required)
- `event_title` (string, nullable)
- `url` (string, nullable)
- `date_display` (string, nullable)
- `time_display` (string, nullable)
- `location` (string, nullable)
- `address` (string, nullable)
- `is_online` (boolean, nullable)
- `website_url` (string, nullable)
- `description` (string, nullable)
- `host` (string, nullable)
- `hiring_paths` (array) (default: [])
- `related_jobs` (array) (default: [])
  - `@type` (string) (default: "UsajobsEventRelatedJob")
  - `id` (string, required)
  - `job_title` (string, nullable)
  - `url` (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 entity was not found, or a precondition failed

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.