/simplyhired/jobs

POST /api/simplyhired/jobs

Price: 10 credits

Get SimplyHired job details by job key

How to use it

Get full details of a SimplyHired job listing by its job key. Returns the job title, normalized and display titles, location with city/state and geo coordinates, job types and work settings, the full HTML and plain-text description, salary (display string plus structured from/to amount, period and currency), the hiring employer (name, logo, rating, company page), listed benefits and qualifications, the publication date, expiration and expired flags, the direct apply URL, and a set of similar jobs.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — SimplyHired job key, or a job URL containing it (examples: "iFcNaKeE120s1UMCNfvZVOsFA05QIBB2r2HOgU2523BjavM4kvFzig"; minLength: 1)
• country string — SimplyHired country edition the job is listed on (default: "US"; one of: "US", "GB", "CA", "IE", "IN", "DE", "FR", "ES", "IT", "NL", "AT", "BE", "CH", "PT", "SE", "BR", "AR", "MX", "AU")

Response

• @type string (default: "SimplyhiredJob")
• id string required
• normalized_title string nullable
• display_title string nullable
• location string nullable
• city string nullable
• state string nullable
• latitude number nullable
• longitude number nullable
• job_types array (default: [])
• work_settings array (default: [])
• description string nullable
• description_text string nullable
• employer object nullable
  • @type string (default: "SimplyhiredEmployer")
  • name string nullable
  • image string nullable
  • rating number nullable
  • company_page_url string nullable
• salary object nullable
  • @type string (default: "SimplyhiredSalary")
  • display string nullable
  • salary_from number nullable
  • salary_to number nullable
  • period string nullable
  • currency string nullable
• benefits array (default: [])
• qualifications array (default: [])
• published_at integer nullable
• expiration_at integer nullable
• is_expired boolean nullable
• apply_url string nullable
• is_indeed_apply boolean nullable
• is_sponsored boolean nullable
• similar_jobs array (default: [])
  • @type string (default: "SimplyhiredSimilarJob")
  • id string required
  • company string nullable
  • company_rating number nullable
  • location string nullable
  • salary string nullable
  • snippet string nullable
  • job_types array (default: [])
  • benefits array (default: [])
  • is_sponsored boolean nullable
  • is_indeed_apply boolean nullable
  • posted_at integer 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 — Job not found or no longer listed 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.