/usajobs/events

POST /api/usajobs/events

Price: 1 credit

Get one US federal hiring event from USAJOBS by its id. Returns the event title, URL, date and time with timezone, venue and address or online flag, registration website, full description, hosting organization, the hiring paths it is aimed at, and the related job announcements promoted at the event.

How to use it

Fetch a single USAJOBS federal hiring event. Pass event as the numeric event id or the full event URL. Event ids come from the id field of the USAJOBS events search endpoint. Past events are removed from the site, so an id that worked before can later return 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• event string required — Event id or the URL of the event page (examples: "5634", "https://www.usajobs.gov/event/5634")

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 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit 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 event does not exist or is no longer listed on USAJOBS 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 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 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 Wait at least 30 seconds, then retry.

Response 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.