/yourator/jobs

POST /api/yourator/jobs

Price: 5 credits

Get one job on Yourator (yourator.co): full description, requirements, preferred qualifications, remote arrangement, salary range, employment type, city and address, skill tags, statutory and other benefits, posting and update dates, and the hiring company with its logo and website

How to use it

Find job ids with yourator/jobs/search or yourator/companies/jobs; the company profile is in yourator/companies.

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 id or URL (examples: "Pacston/12227", "https://www.yourator.co/companies/Pacston/jobs/12227")

Response

• @type string (default: "YouratorJobDetail")
• id string required
• url string required
• text string nullable
• requirements string nullable
• preferred_qualifications string nullable
• remote_types array (default: [])
• remote_note string nullable
• salary_text string nullable
• salary object nullable
  • @type string (default: "YouratorSalary")
  • min number nullable
  • max number nullable
  • currency string required
  • period string nullable
  • is_negotiable boolean required
• employment_type string nullable
• job_types array (default: [])
• area_code string nullable
• location string nullable
• address string nullable
• city string nullable
• country_code string nullable
• tags array (default: [])
• statutory_benefits array (default: [])
• benefits string nullable
• posted_at integer nullable
• updated_date integer nullable
• company_alias string nullable
• company_name string nullable
• company_url string nullable
• company_image string nullable
• company_website_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 — No job under that id 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.